Status:
Finalized
Timestamp:
161 days ago (Nov-06-2024 07:47:11 PM +UTC)
Transactions:
191 transactions and 102 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.077983578109151824 ETH (0 + 0.390195159829665775 - 0.312211581720513951)
Total Difficulty:
0
Size:
77,865 bytes
Gas Used:
17,410,917 (58.04%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000017931943603 ETH (17.931943603 Gwei)
Burnt Fees:
š„ 0.312211581720513951 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,724.61 / ETH
Hash:
0x7298fe1c49ab6c27a2fb8bd464ad7d99084415b1b5a91921c26fa6df095035a0
StateRoot:
0xf8b3f21525079ce45e09ad750cef42184081f5c2d83b22aa808effe01273dc48
WithdrawalsRoot:
0x7db38cade3f1a23bf1a4b47b57a795abd2401b4990a71e69748644fd20111917
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x44c2d9fbe77a77eaca9c51315f8833d6d1e1a6f871e2fbdc1a220e960c5f74b9
Parent Root Hash:
0x5c49e1899d02a75f40567d977be02b86be79a1b8efb5196e67f7c24a77da3921
Beacon Chain Deposit Count:
1757515
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xc482a4ac12326e99e10596d84dfc08e2fbf32f673cda7aa54907851ff74a9856
Randao Reveal:
0xb89083876494b7806380d752f39e8dc1ba1555541713b112e36459425fdb56b794560145e01083011a6d9893014b9f180a4c3f32f6903c07f1d8f1ce09bd3aa5530bf7b7da5b1b86b7bdd6cde7088a777e796f4656f2413354cb2a18d6c1d705
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.070160644056294918 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
0.000000005663462761 ETH (5.663462761 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.