Status:
Finalized
Timestamp:
160 days ago (Apr-24-2024 02:47:59 AM +UTC)
Transactions:
117 transactions and 52 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
2.100445781022284498 ETH (0 + 2.36218512349085252 - 0.261739342468568022)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
82,622 bytes
Gas Used:
15,835,282 (52.78%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016528871571 ETH (16.528871571 Gwei)
Burnt Fees:
š„ 0.261739342468568022 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,139.10 / ETH
Hash:
0x1c39a3d5dd0c9f951c6fc722a7d6717949a836f55b97718e0bb613915d06d085
StateRoot:
0x85b176ad738cd7e6b0ccd216a4f0b777f800306bd702955845ea4d36a5cd7878
WithdrawalsRoot:
0x56fdccd49afc379f90de5f7d7df3387cafe27f85f85ce9c3b1cfef44a5b5ac63
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1768108b34a492f1f9a61f5e31227d0231400237ec652afba0635e8dd0d20215
Parent Root Hash:
0x488f1474eeba301d7305b5074bfc1fb0b7857c950762af0ee7fefe6606086c75
Beacon Chain Deposit Count:
1452205
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x35706553353d00dbc8bd08306ebcec2e35a78c306e32b1628de380edf26eea60
Randao Reveal:
0x953b9ff3d45cfea8c0fa134e99c0092230d9073518b26b5efc6efd28bbd3d29f043dd4f6ae7d48857f518368dc7892f80169c01d1c9a77349298be144b0fc38c397eeef3b75fcedcb7a26289c51c99c22bdeb7b7dfdc301b9d2aa8719b9d6cf1
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
1.539148970017412364 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.