Block
#20062218
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
639 days ago (Jun-10-2024 03:06:35 PM +UTC)
Transactions:
233 transactions and 109 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.115181309309116495 ETH (0 + 0.427805891395017963 - 0.312624582085901468)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
96,784 bytes
Gas Used:
19,262,962 (64.21%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016229310014 ETH (16.229310014 Gwei)
Burnt Fees:
🔥 0.312624582085901468 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,665.99 / ETH
Hash:
0xf7e1c3cef34ec71eaff9b33acc7b1126344909d71bda67fd506def821fbf4b6b
StateRoot:
0x4c82a7d5457b940266192e94dbbe3fa0bb65a6a436d62d9d05d9f550537b08ac
WithdrawalsRoot:
0x69fb611d1763b1cf918271ed61e9977f7599d564dfa1b65b5b361a0c0a5de03a
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xcb93477b7a1533df21bb38fd770fce7acad76caba7f6dfcb4c94b64d5e26583d
Parent Root Hash:
0xd22bae7dbd7b7e8c24a4daba7c0c05d95c6cdf0d05a4ae374ccdece8ecef3daa
Beacon Chain Deposit Count:
1527435
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x001d80e2d1992280f829e37d78afefa0ec68f63b8c1799deb6b3b368cefd21ed
Randao Reveal:
0xab9afc8b5aa089fce8a0dd632a53b83103b33414c4dd0967aa3d9169fc607291a2f4434a1e5a318c303d4f9859c93690161de163ebaf0c6be596e52639b96637937aacbed3545ab98ce2cd7d3a6a472823106090509a91d488ad2e6947924635
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.089032562659130671 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.