Block
#20055440
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
637 days ago (Jun-09-2024 04:24:11 PM +UTC)
Transactions:
131 transactions and 85 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.048963452293915356 ETH (0 + 0.164650546887566832 - 0.115687094593651476)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
70,320 bytes
Gas Used:
11,750,012 (39.17%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000009845700123 ETH (9.845700123 Gwei)
Burnt Fees:
🔥 0.115687094593651476 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,706.00 / ETH
Hash:
0xcf790e2ee2ecd0d2eaf8fbff9e5a0040b0e9bde6a6e375a849f951a833c592c8
StateRoot:
0xddd150ee00ee793f9dd0cd1dfb2c77877834afb8aa4dd823894b90bedd3db954
WithdrawalsRoot:
0x16f16a0f3b5dcba32422a66e24a2ae15a9cf88ef3f2cbc712eddf826e1fa087f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1a8c0459592e54845b0b64e959c57ddc11f3883e0a0f9f33424d9ba3c7917652
Parent Root Hash:
0x687af8abd3cab59ded5e9a187145655022e962f6c785e2658e3d9869e05e72bd
Beacon Chain Deposit Count:
1524377
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xaa8c207bbab9d1e5bd6476e65a0053aced5eec6ab01c8dcfd15e0d30d0aa2ff3
Randao Reveal:
0xaffbb6d496f4d57b3a43323b4c499305075766a4601fa4590cb1efdfd7092e5adddf4f7d34206af71bb1581bd4d66b2706b253be7b1bf6acfd6b136eea8108113ec4946cf3da4c2dbe45d895b2e4109279a5fb90fccb39c52219606d0484e453
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.044105505761513745 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.