ETH Price: $1,884.31 (-4.49%)

Block

#22600575
MEV Block
EigenPhi
Block Height:
22600575
Status:
Finalized
Timestamp:
268 days ago (May-31-2025 05:18:47 AM +UTC)
Proposed On:
Block proposed on slot 11820392 , epoch 369387
Transactions:
Withdrawals:
16 withdrawals in this block

Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.02042795949565831 ETH (0 + 0.04376407466249239 - 0.02333611516683408)
Total Difficulty:
0
Size:
132,766 bytes

Gas Used:
30,073,264 (83.54%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.00000000077597547 ETH (0.77597547 Gwei)
Burnt Fees:
šŸ”„ 0.02333611516683408 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,529.32 / ETH
Hash:
0x474a2114b85b2d565f64e401c0a2ebec1694bc3c21ca842798b2d5b822da4ac8
StateRoot:
0xe8f4671621555dfd22d47024f1a9d7ad250398a7e6f3bc7ba4a86f02639f3d23
WithdrawalsRoot:
0xc1cb7d0dc7b54de26fe6efef106d90189fcaa881b60660dec5e112640e20cff1
Nonce:
0x0000000000000000

Slot:
Epoch:
Proposer Index:

Slot Root Hash:
0xd65fe96aae04a1dde8604dcb8a49b903aa0f186410a09f966fd28968d9e7ccc6
Parent Root Hash:
0x1b21134e179131dd048aa2d838399b123e024d0f113a465462fdf7304864ff00
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xdbe9b56287e81c803081d86235ec96c0bf3e4bcc74729793eb4f3a3f7925adc3
Randao Reveal:
0xaf6d0f0690b3a221ad9b6c26b39b5668b16274290fb761f1810f567412cd46e892a72e0cb4e936386c50c38bfa93135916bf96dada496ffd3736653657784e50137c2002300f864b26bbb6f64d1ae3a31ddf3204b9d1b50c7aebb477939a4f13
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.018457014666104539 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.