ETH Price: $2,000.13 (+0.09%)

Block

#22516337
MEV Block
EigenPhi
Block Height:
22516337
Status:
Finalized
Timestamp:
313 days ago (May-19-2025 10:11:59 AM +UTC)
Proposed On:
Block proposed on slot 11735458 , epoch 366733
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.042935134645920107 ETH (0 + 0.054410651338288467 - 0.01147551669236836)
Total Difficulty:
0
Size:
78,732 bytes

Gas Used:
12,535,121 (34.82%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.00000000091546916 ETH (0.91546916 Gwei)
Burnt Fees:
šŸ”„ 0.01147551669236836 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,528.66 / ETH
Hash:
0xcdfc1d56c39c8ba850daa192bbd6bf9e4f75d0f0a56b1dc394e7d04cfa2e9d20
StateRoot:
0xde74252ec5104a9224ffa87a7d33b53a2fc7d569834c8a460509b0d08ab1b818
WithdrawalsRoot:
0xa936b464044d24f4134770016e693f0d4a7b8e175a314ce60bd18a4894bf347a
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0x777a3055a53f6862afbd74a5cb747e949818673aac51991b6ddf0874e6c40097
Parent Root Hash:
0xe7469215a380ef0fda65779e8249329776f2a52374431d9dbccc0957012e092a
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x2ee256ec6f169a3ee3eb36e9daf610b1b42d9ea38dcb5b44caf431934889a1fd
Randao Reveal:
0x923d19933a371bd62d48618a171d283aa85e2dca8c8023ecde786624bd26477372bcfa79c74d4ac62a8f2157168f77e705921bfe44940a4a2f3fe39e193d917249290ea6287ddae88358ea21975a87e8d0541474c3be24472744256e4fb8b736
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.036975899171806049 ETH
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:

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.