Block
#20092817
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
619 days ago (Jun-14-2024 09:45:11 PM +UTC)
Transactions:
226 transactions and 91 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.032322459149607991 ETH (0 + 0.207980903351711281 - 0.17565844420210329)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
85,558 bytes
Gas Used:
17,437,990 (58.13%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010073319471 ETH (10.073319471 Gwei)
Burnt Fees:
š„ 0.17565844420210329 ETH
Extra Data:
rsync-builder.xyz (Hex:0x7273796e632d6275696c6465722e78797a)
Ether Price:
$3,479.74 / ETH
Hash:
0x78379f670ab4e3db9d115e7012c187c39dee50375ea28d787a99597573a477ba
StateRoot:
0xfa77f9b6e9906c56511668fee8f392671198bbbf30721c7dc2b0c9b3f9209267
WithdrawalsRoot:
0xe46c05aea819eca8570679db1465f7b70ec74f9e3437e9314b7f5f2b8db85217
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x2865f9a6cecd465f3080f122c6aeacc4513165bf6f1dd09d6d69c5ac50be9721
Parent Root Hash:
0xbb95310f364c0d98492e3338bcc203b53eaffa40b402f763ef1ce2b0e4179671
Beacon Chain Deposit Count:
1537748
Slot Graffiti:
Nethermind for Lido TKcdcb (Hex:0x4e65746865726d696e6420666f72204c69646f20544b63646362000000000000)
Block Randomness:
0x2efc67f3e977b36ef52e4894a7fe2a3bd41c0c8389b11f63a8baf3273b857d48
Randao Reveal:
0xaa4e3d132397bf9c1b1ffc2799892ad34030d35cff40cca0abaa273016b55007f32fb23a8026621b709759ad16aa3924019a12bcab1a300006a40e7d9b460c07f20df2bbebe3d5c946dc4f9bebf0081182d612095f08097adbc202362dbad5be
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.040861901652125792 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.