Status:
Finalized
Timestamp:
118 days ago (Jun-05-2024 03:03:35 AM +UTC)
Transactions:
171 transactions and 274 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.068552340483100111 ETH (0 + 0.259885728947046679 - 0.191333388463946568)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
96,997 bytes
Gas Used:
25,108,396 (83.69%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000007620295158 ETH (7.620295158 Gwei)
Burnt Fees:
š„ 0.191333388463946568 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,866.46 / ETH
Hash:
0x9ec1aa09163965db816dd3d7496aec4f1c2ab3728c424c01858026e5f9f497e6
StateRoot:
0xa90c78b9dff7275ba38168bf4268eac6a0600d5d1f5a82bdd3d4874850dcc41d
WithdrawalsRoot:
0x51c877626e8527c33d6db32eae346f6f38bf407380c9dbf997f5acc45065aa22
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xdbeffa89ba545c7f61c247ca74a067996cd0a96d365870d893159ae280ba2d8d
Parent Root Hash:
0x74441e86adedb7de2336ed97337e4da08c33236c2b24820416cba66885815a1d
Beacon Chain Deposit Count:
1513749
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x501732b0722a779e951bb69ee61d136b3654fa5cd015e920a6602b76a534eb6c
Randao Reveal:
0x91efedcc8cb651b9e6059458360440f15dc791a7ae75fd14c22e893b8b4a8678216f33981c1846f796e47d0b6a2d781a122d354b1bffbc0f7be2c47e995a90ad9788e759c21fd8a155ce3a5703a6ed4927dcc9f387d35358e75bba654b0cd23e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.065660522431837441 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
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.