Status:
Finalized
Timestamp:
14 days ago (Jul-08-2024 02:49:47 PM +UTC)
Transactions:
282 transactions and 142 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.085763205649653004 ETH (0 + 0.422715516288774554 - 0.33695231063912155)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
122,279 bytes
Gas Used:
26,956,610 (89.86%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000012499802855 ETH (12.499802855 Gwei)
Burnt Fees:
š„ 0.33695231063912155 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,018.49 / ETH
Hash:
0x30334a5bb9a1c668ea438b130ae3ac1f4ba8337dd6e9b571c8734549b92560a8
StateRoot:
0xf7d5396096cdeafc7b41d38a41be4b9dbed195751e05e410ee738b9f5467965c
WithdrawalsRoot:
0x26531f69c2e249775756d9476e3675aa2f4ed702611a2db74d994dcb1833f460
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf1aab5e1dafdc466c15688842d01602ef83dcb098f9b20e82ea0cd8d1318f611
Parent Root Hash:
0x044c6056f4aaf2500854b77c923d9d6e447c17caa8559bb1f377f15b772cc403
Beacon Chain Deposit Count:
1574496
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xd6dd26e8fd3689862720175726801afff437f848a0de0138b8fcadc386e2179c
Randao Reveal:
0x840375be4d23d714026282c08e00fb7f701e0f3d6fad46f2c38ca19f5710efcee6cbd4df17747d9eb5a9a272aaae0f110640ae412cd91f8ef23ea32803038420cbfabbffeb6061d007e1c8423d1802e1b7bf1b4fbb697e5a8c6f7d89a5c81354
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.080544554726780129 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
140 wei (0.00000014 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.