Block
#22458363
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
303 days ago (May-11-2025 06:37:59 AM +UTC)
Transactions:
39 transactions and 43 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.040600480302226903 ETH (0 + 0.058076954123704767 - 0.017476473821477864)
Total Difficulty:
0
Size:
31,870 bytes
Gas Used:
5,640,356 (15.67%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000003098469994 ETH (3.098469994 Gwei)
Burnt Fees:
🔥 0.017476473821477864 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,514.75 / ETH
Hash:
0x400f9d8ad7c6db4f913e38dee9dc2aaeff90014d371fe14f066a1fa440a8af3c
StateRoot:
0x3d3ab1c887f06b9886a4efbf5c27de3e3894e8fd1f30e27bd5394bc0380065f2
WithdrawalsRoot:
0xe4d6721f69585f3ac215dc4a54d890ccde329496fd000dc1558f562667882c56
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xcdf6b967f9ebfd1c765ef6fb23565d38252f487c388f4bc63d6609f8b3516a05
Parent Root Hash:
0xa9b9fe6fe14826bc7c48284580ab631337d6b8139a5abe42919cabb20bc91913
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x91de424581d11da19f45656ee2509c1788ee91dcfe2e933dea650edb7d82dd2e
Randao Reveal:
0x851f6ac5fec4f3ca1d669787b898ca73c0c69ca80dba4dc06416bf8dc38c4dcce882b17ed2a1ef36b8619aefa7c6f513189028c443122897913549780911c81dca90afdc6b1da0f0100cc3c9ce81062e1d3d02e847b5cd902c74a68deb6ccaed
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.029386718356778414 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (33.33%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000393216 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.