Block
#21562180
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
289 days ago (Jan-06-2025 01:35:11 AM +UTC)
Transactions:
262 transactions and 130 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.073416789827307844 ETH (0 + 0.254368429577448064 - 0.18095163975014022)
Total Difficulty:
0
Size:
165,748 bytes
Gas Used:
29,992,948 (99.98%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006033139515 ETH (6.033139515 Gwei)
Burnt Fees:
š„ 0.18095163975014022 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,688.83 / ETH
Hash:
0x41b180595bf3416275d38ccfa7b810bf732133b0336bd7d22c1c9ed0e0665c9c
StateRoot:
0x315d7631645a17ac5caa509a18a18366ce27ece0f76dba8d126409e7cfbdbea0
WithdrawalsRoot:
0xa8bdabb5b4fbef0e3d7564b84b5125fc626124bb5060f0ad5d41c00721378f70
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x40bada6bfe44cfe8d85bca8f6376b506e0d374ebd72b715d6c40e6742b987e1f
Parent Root Hash:
0x90b981295202da4956ab62239f9c729ea4d9e013839cc26bb4b53561706e7ca1
Beacon Chain Deposit Count:
1849866
Slot Graffiti:
Lido ā”ļøAllnodes (Hex:0x4c69646f20e29aa1efb88f416c6c6e6f64657300000000000000000000000000)
Block Randomness:
0x67cd25b36a2d19eff71183ee497f03f1ab197452651bcde98ab9f934f1688ea6
Randao Reveal:
0x805baafda4aaf4830a0d541d50c465117089d32870e01f5e55b6bb08cadf2b350dfbe61d526899651211d295b9bd6be017f4e4803769956e73a58b3130020aef1d005a7e6c600ecbc857b52a3f6d1d5275d1302229d7f6902dec49a442524285
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.072800037454312394 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
26 wei (0.000000026 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
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.