ETH Price: $2,323.98 (+10.69%)

Block

#22304395
MEV Block
EigenPhi
Block Height:
22304395
Status:
Finalized
Timestamp:
331 days ago (Apr-19-2025 04:58:59 PM +UTC)
Proposed On:
Block proposed on slot 11521493 , epoch 360046
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.012938517232752 ETH (0 + 0.0186753022617941 - 0.0057367850290421)
Total Difficulty:
0
Size:
81,798 bytes

Gas Used:
17,118,380 (47.60%)
Gas Limit:
35,964,742
Base Fee Per Gas:
0.000000000335124295 ETH (0.335124295 Gwei)
Burnt Fees:
šŸ”„ 0.0057367850290421 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,612.74 / ETH
Hash:
0x95309b3e30f9b0141acae3e1ac66b05276914bcf4069c7abf04fe8f33ddbea1d
StateRoot:
0xfde7dea41a754e825c3e72fd1cae0b5ab37542204ff6ebc95393da397586133a
WithdrawalsRoot:
0x423680610e0cbe92165d61da380503e7da36a8b7a056895625e85c7381d5c8bb
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xf36cc5e1c012dbe69a2ca64d628ccaa17c4781290303b691144ce0b4cfe85908
Parent Root Hash:
0x20a7162fa090fb0bce95dd911fe47918884dd92545cc2f52a18662033f136f59
Beacon Chain Deposit Count:
2023838
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x628fc4f405853b8349aa8b6242b435b7a842cbcc0f9db368990102b340e55e4c
Randao Reveal:
0x93c0a848771006c5eb354bf048876f8bc0930ad4d797586421b14fc389b4bcb903795213678b5f0d04aaf35de34d56b8029a3b6aff4533eacd3f0bc96d38e6d3dc0cc8188377617bae5226eb5e2612c597408a0655ea08310986352957f8e554
:
:
:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
0.000000000067040434 ETH (0.067040434 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000052722742591488 ETH
Excess Blob Gas:
60,162,048 (459 blobs)

Blocks are batches of transactions linked via cryptographic hashes. Any tampering of a block would invalidate all following blocks as all subsequent hashes would change. Learn more about this page in our Knowledge Base.