Block
#20622952
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
559 days ago (Aug-27-2024 10:36:47 PM +UTC)
Transactions:
116 transactions and 46 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.396675536490542133 ETH (0 + 0.505516487869515879 - 0.108840951378973746)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
58,940 bytes
Gas Used:
11,234,754 (37.45%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000009687880249 ETH (9.687880249 Gwei)
Burnt Fees:
🔥 0.108840951378973746 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,458.29 / ETH
Hash:
0x8740e36bd05a6dd00fb894c2ef27b3a9acee7651054bcc1a6c53b4ed9a37380f
StateRoot:
0xfafdb07be2178fffc5ee2b1ac2eb81fe24b760f915ce3bf2e4d91579be33fe75
WithdrawalsRoot:
0xb9f694cb44de26224f7e998ad30dcc8cc926ae6559a3a11b4d64e36ed99eb684
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xe6a42e21c42ef43046a3d9f25edf8cffbd0ce0e43c9d1cd91411c91d9310c4c6
Parent Root Hash:
0x9c5addcd291a34cfdab7a7f94996242bcd1fb0c0a73413e57dfef623cb70ddc5
Beacon Chain Deposit Count:
1656407
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xa88fbc2d7b7455a0966aefc9051a30dd0236c101e884720641c8e97e7e7f0648
Randao Reveal:
0xa7f1b13d6bbe94e2c2709cd3f37ccb235d1a4f3497e2b9f4fb925a410caf05d1d5faa8ec6886a61b87309fa9dbd6dfa4175faf95837f5a07cd7416456e2c94dbe649d2beeea9a33b3ce642b8b551ea775a070ad33d0231906ff19cd0ef39588c
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.087849594653718196 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.