Status:
Finalized
Timestamp:
190 days ago (Jun-07-2024 04:59:23 AM +UTC)
Transactions:
152 transactions and 52 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.024353527027919971 ETH (0 + 0.105646715254479946 - 0.081293188226559975)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
65,392 bytes
Gas Used:
12,051,895 (40.17%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000006745261905 ETH (6.745261905 Gwei)
Burnt Fees:
š„ 0.081293188226559975 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,676.79 / ETH
Hash:
0x4d3ecf98da67550131cb85394d9882f42246937f33fd10e5991180bdcb5571ae
StateRoot:
0xa20ca9cd976d75e34e3060624f30c3502cea4eb4701f382068cecd2b8c14d52d
WithdrawalsRoot:
0xd24b1223ad9aed2df398a68f1eb466ec30c9e5b51dfeb0ea150facebe386c7ab
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x3e95fb2f085b309eb4c082095aee87568bf00679c9743b22cb086da8bfacc763
Parent Root Hash:
0xd7f9d8096dfd8b3e0a1ee5cad2a7cdc1c813125a1f10d44e1a6f1db63d22f390
Beacon Chain Deposit Count:
1519845
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xeddd1c0bedc22b2a4ab391c58772c162f53336ab5494631e7c5aee1f87aac0c8
Randao Reveal:
0xaed4608f889663becda988ea851768b89d95d7e3d31bf4c79fa795fcf0a0cf2deda13f419dad199989d7f83dedaaf3ea187b8fc41aa151e63a1e9db9447786ba36cf65add006490b3589fa7b4e81eb19632174045b41483ceef2b9e780e24d6b
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.025523991637589285 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1.00 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
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.