Block
#20685871
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
530 days ago (Sep-05-2024 05:26:59 PM +UTC)
Transactions:
27 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.0946900494029555 ETH (0 + 0.11264171866514358 - 0.01795166926218808)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
21,677 bytes
Gas Used:
5,285,242 (17.62%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000339656524 ETH (3.39656524 Gwei)
Burnt Fees:
🔥 0.01795166926218808 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,367.89 / ETH
Hash:
0x0909df81c1a1abd33e75a9ec09f6008771fa323ce83425ef1152bb0402f82f63
StateRoot:
0x982a07c7a01de6bc54403cc4f7b3fc04b2a49d1e48d369210456f6d5bc646405
WithdrawalsRoot:
0x204eebd6b05a2154f69770ec1ffafedee3fc7ab71424e7779a6ac67be38dc232
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xfe7184088c6bb95206279772bbefca5b393851a7c463809616639a0de80a09e0
Parent Root Hash:
0xe5e1611c140249dbff82a292d855235531629a1d3dc04d037d42730a7bdf2eb7
Beacon Chain Deposit Count:
1672223
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x9438c08e83807c07abc315bf2a85380bc9a6f19ed6859464ff3e7263573ad498
Randao Reveal:
0xab37adb25b30b4b621c0645421b81491a24c6ff2045b63a3217dfb4ddc49c040f961e49ee73d7895f9395f7b83a366d014de519ff4c21bda346ee09ab99ab3aa91e523e3b91ff3e8ba347206743f299c4460527aa25ad258be200b1596956e71
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.095644596878013093 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.