Block
#22648927
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
253 days ago (Jun-06-2025 11:47:47 PM +UTC)
Transactions:
183 transactions and 136 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.08403242220799422 ETH (0 + 0.115232223646567708 - 0.031199801438573488)
Total Difficulty:
0
Size:
96,059 bytes
Gas Used:
17,704,127 (49.18%)
Gas Limit:
35,999,965
Base Fee Per Gas:
0.000000001762289744 ETH (1.762289744 Gwei)
Burnt Fees:
🔥 0.031199801438573488 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,478.31 / ETH
Hash:
0x7b42151f99cedee56ef65f625fcc6c51629becd499cb0bd56a7d15cf47312772
StateRoot:
0xcadcc9cdea0f287cf70945fb55431637c7da42f9d9c6c7d499a854b53de24621
WithdrawalsRoot:
0x02fdb6969b7d97713f3a0ba096994b7047f924493b1f1afbb3252291bcbbe116
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xad182f9ea02b4db941a0609aa055ac810b7ef05aae423fe63db33c0bc5e37e46
Parent Root Hash:
0x73dfe1d4d91d06524785b68fec56f2d189baa671e5c8cbdabed081949434f430
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xc86912e7ae726fed81b317046178b061717d541f35424821b028c1d558d656e5
Randao Reveal:
0x819be1ba45576d77ef8cefaf54c2d29b755bd7e3a61ddad5b26cadb12139054b6be68bff774d6c1f6462dfa4fa913f770d8cfecf2408db15fe324a9201ebbdf3baa0ff026a8adccdf22acc066e6ec727420493ebb93352938caec1fb690ad225
Proposer Fee Recipient:
0x4675C7e5BaAFBFFbca748158bEcBA61ef3b0a263 (Coinbase: MEV Builder)
MEV Reward:
0.051696064545174198 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
1.125 MiB (9 blobs)
Blob Utilisation:
9 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
1,179,648 (100.00%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000001179648 ETH
Excess Blob Gas:
393,216 (3 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.