Block
#21846468
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
368 days ago (Feb-14-2025 06:24:59 PM +UTC)
Transactions:
196 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.024780470397133938 ETH (0 + 0.060941927961545127 - 0.036161457564411189)
Total Difficulty:
0
Size:
78,386 bytes
Gas Used:
14,666,147 (40.94%)
Gas Limit:
35,824,433
Base Fee Per Gas:
0.000000002465641287 ETH (2.465641287 Gwei)
Burnt Fees:
🔥 0.036161457564411189 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,726.02 / ETH
Hash:
0x5d37ead27060143ab904381abcd7687de0e501b76c2fb4b2a782d21ba7a834bb
StateRoot:
0x10c6e6b2dc9716e3ce537dd45f7a3d3e13e0b4a6033a5e7dc9d673a1d335e26a
WithdrawalsRoot:
0x2e1d29b059a71e5f7951139b7674cf45245b8c61ad96be0b36f3bd17607cd1e3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6771979747422d91799f50c4ef9bf0ba62e6d803776ec369d5c84dbf10edc633
Parent Root Hash:
0xf3140a21f0ef0aacfb3e8968b33aabaaed7457353d05201b460c4c143bb166cc
Beacon Chain Deposit Count:
1912094
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x6a262e7b11b04644185071d691db2b2daf16960531b5e12ead2f0fa34eb432ff
Randao Reveal:
0x9294a16777aef24e845d7075ef409a274ddb6864e30ffbc754004ea12637a33dc4084e70129d52ef0289c983f30123830ea020c6742f6017a0809fd689ee69aa623fc810c2e9deae67af5cc5e6624ad0af77cd88a4017050c513d9644ff6b662
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.037179711942744668 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
0.000000002207302337 ETH (2.207302337 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00144657765957632 ETH
Excess Blob Gas:
71,827,456 (548 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.