Block
#21649038
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
402 days ago (Jan-18-2025 04:39:35 AM +UTC)
Transactions:
99 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
MEV Builder: 0x563...cf3 in 12 secs
Block Reward:
0.008339032191996285 ETH (0 + 0.097089808569883161 - 0.088750776377886876)
Total Difficulty:
0
Size:
39,318 bytes
Gas Used:
7,345,188 (24.44%)
Gas Limit:
30,058,561
Base Fee Per Gas:
0.000000012082846127 ETH (12.082846127 Gwei)
Burnt Fees:
🔥 0.088750776377886876 ETH
Extra Data:
ك
�geth�go1.20.14�linux (Hex:0xd983010d0e846765746889676f312e32302e3134856c696e7578)
Ether Price:
$3,304.42 / ETH
Hash:
0x6fb7e905e661707e12e56c0850d10e4cdbeba3d77f154402429f4e51f1c49f45
StateRoot:
0x1aec47a4547210429b8cbe0515156c316a98ad9ce426216de47523f468813c67
WithdrawalsRoot:
0xdc2c4771ebbaea5260cf0746492b7b66e5749b7aada881aecf703ecaa49054b2
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x749ec50b548795dab119b72527a50ee76e7dca6e783fa4a4f0eb8a2eca0707e7
Parent Root Hash:
0x7b7c07d8057c351b6a41d920b960b2c38c8a12711bb3532b1120173a1991c6bb
Beacon Chain Deposit Count:
1870030
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x4ccfde30f1abd6615a310918f6afd3c400484878c67875c625fbeb08fcd55532
Randao Reveal:
0x93327e8e1ada294bc78e6c260c724f5520a99a8b8a426b78ff4430d4b00b4efa480bb94ebd30d1398b7b7de5b74caa60027b5663bd2afcfcc67001bba7addfec2ec15d5da3cd43e609d9d6d0e9e28fc3686ef184f51c08f8a96a41eb704e36c6
Proposer Fee Recipient:
0x167E7644a25377544d83FF60672C89831bf2Ac0a (MEV Bot: 0x167e...c0a)
MEV Reward:
0.756523313881711754 ETH
MEV Payout Txn Hash:
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.