Status:
Finalized
Timestamp:
150 days ago (Jun-06-2024 11:09:11 PM +UTC)
Transactions:
179 transactions and 98 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
*rsync-builder.eth in 12 secs
Block Reward:
0.040270431039934877 ETH (0 + 0.251104000806683513 - 0.210833569766748636)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
70,144 bytes
Gas Used:
15,888,129 (52.96%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000013269880284 ETH (13.269880284 Gwei)
Burnt Fees:
š„ 0.210833569766748636 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,812.05 / ETH
Hash:
0xe525dd3e258591db83d7b1864a1b9fb5f5fa3cfc924418c69a037842d2121197
StateRoot:
0xa492cd336f351836967a934e3d5bd49af5a337291adf0ae1890ffa2f287ad9c0
WithdrawalsRoot:
0x48bab24fbe033f2b00f60d7e2d0d7cc1facd5cd69c5ef3f42aad8bcde0af88a4
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xbbd4c25f72bdb79706682cc420a04cc1ffbad6e64e575dee65e6f8b51f2c12d3
Parent Root Hash:
0x1908be25a4c94a769ca8d595b82c7bfc317ae561d2e440b24a7881a372d59016
Beacon Chain Deposit Count:
1519678
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x5d86f45a856bae1563f6e0b219267e5168cde4a18dafc8e169c73b5fa9abe097
Randao Reveal:
0x88399b6bac29ad78775959207308eb0218d322302bf769340c2a22be6bed68d04717ddb4807e59784509e48a4db6c6e103147cfa63d76e4aed872fd542ffb6926d57acffc2747d75ca2f1f72912380847082e58eaaa6da81ccce2e6096ac323d
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.069807439481801508 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2.00 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
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.