Status:
Finalized
Timestamp:
168 days ago (Mar-18-2024 12:17:47 PM +UTC)
Transactions:
317 transactions and 80 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 24 secs
Block Reward:
0.095740198238986957 ETH (0 + 1.637310286975120714 - 1.541570088736133757)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
126,555 bytes
Gas Used:
24,645,861 (82.15%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000062548842937 ETH (62.548842937 Gwei)
Burnt Fees:
š„ 1.541570088736133757 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,520.31 / ETH
Hash:
0xe6c758ccd878d044956cfef5dc69ebd61280902967286a08c2c079422ccca916
StateRoot:
0x818eb9c979eef226d744cbbec19eba2a4c5aff10a23d7e071250776e2e62df04
WithdrawalsRoot:
0xa9f889d9a0518d695e04f4f76048bacffa16b0ee25ebcb399e0ed2a5d835c39f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x91ab66ac6294cb1be3c376d74e601b4e509881952f11e3536b5491a82e47d765
Parent Root Hash:
0x69b6f30f52d3520c277390aed9c0f4c90f24ea4536af3b7b0fb86a2460d7efdc
Beacon Chain Deposit Count:
1356835
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x3b0d57fe09963739106a710d3bf405b39ea690ba3ef088975768f00abf7dbbb9
Randao Reveal:
0x83e01a0d7528446dd1893d4585e6cefa0fe9ff1c8ddc8313591ecd6597e3d163825979b521f297d9aae7a9a307bf64c90a7c087be0c32e0d60ccece43c0ac8925c2ad231e41e1c1af1da87873f2280c6627f7f9a4ae8ec57792a4b733487fb93
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.090623358319813038 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1.00 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
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.