Block
#22679516
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
251 days ago (Jun-11-2025 06:25:35 AM +UTC)
Transactions:
208 transactions and 50 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.010682113896109605 ETH (0 + 0.032726999217663569 - 0.022044885321553964)
Total Difficulty:
0
Size:
72,648 bytes
Gas Used:
14,180,486 (39.39%)
Gas Limit:
35,999,896
Base Fee Per Gas:
0.000000001554593074 ETH (1.554593074 Gwei)
Burnt Fees:
🔥 0.022044885321553964 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,772.57 / ETH
Hash:
0xd28f9532ece48c269e00729e136bcfb7534d66eb8c4d5b364151e47a2797d2d0
StateRoot:
0xed9cfa5c1d60e608be671273b47f2e1eb70e2323ef0785578401e3233165e0d5
WithdrawalsRoot:
0x8a8aff3fb47edd33d99d11acffab3d98319730475811f3e5472dd0743ea69c75
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd2097d5c474cadf0190ed5e8a890d436ace4f478e1fd5fc587a86f0cbe70fe6a
Parent Root Hash:
0xc3474d9a1f9c296f53a4d3643b7e4bd7fe0c76e489373a6cb906da7021567eb1
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x94561736a70871bc04f45dff881dc775bcb1eea1e1828229f979e1d492d5ff94
Randao Reveal:
0xb4fb02f8015052ad411c083f663a3f6aa72b28f94cba2785cb0cb0a7fe98b0c181a2bfce253ef1c11de575ccd81e01f703c996226e4c1ca3221d51f0ca6c523cae395e2bb662d741e818b969e89394f98e2f87e60231676e2df9c765aae09821
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.0095770709078351 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (66.67%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
0 (0 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.