Status:
Finalized
Timestamp:
232 days ago (Jun-11-2024 05:47:35 PM +UTC)
Transactions:
233 transactions and 81 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.025467785285258823 ETH (0 + 0.309312883909302351 - 0.283845098624043528)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
104,221 bytes
Gas Used:
19,482,488 (64.94%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000014569242831 ETH (14.569242831 Gwei)
Burnt Fees:
š„ 0.283845098624043528 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,497.32 / ETH
Hash:
0x8e92c47c812273fc4da56cc91bc0b2f8285e6c6090c11bc75cc8321aa5a25850
StateRoot:
0x2bd529be07c8342ca83b801ed50c29d4bf05169bf80c088609a31e4b050ae1a4
WithdrawalsRoot:
0x065ab61fe6d32f899ffaac03bea8bde565b2ced53cd9ed7b2b297990e1f81092
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x997ca2817cef27271cc7edbac8f1fa8125e270fa20986c2b5035a1f470e2d3ec
Parent Root Hash:
0x1ab0002708223673fc130e5370e5e999df56ee6b01d4ea83247801bfa13e671f
Beacon Chain Deposit Count:
1528705
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xabc5f26bf6a68aaa0f045cf9beb123a43210a8bca7a5959626b4ea3d8128f57f
Randao Reveal:
0xb8c589e3ba730c01ec4fe61004f07b455da2c654d32fdaeb3b9df6ffda5d09c9e88f5382746ce299ccb271caf2c6b30501250f4f6b3c7da88bf7fcf5179fe146a27cce9591a306e61238ab639cb34d1009d1332a66985ef2a1dba69cbd2309f4
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.026229181806764915 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.