Status:
Finalized
Timestamp:
102 days ago (Nov-06-2024 06:02:23 PM +UTC)
Transactions:
159 transactions and 64 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.023595753273893858 ETH (0 + 0.244214746014981049 - 0.220618992741087191)
Total Difficulty:
0
Size:
77,527 bytes
Gas Used:
15,795,887 (52.65%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000013966863193 ETH (13.966863193 Gwei)
Burnt Fees:
š„ 0.220618992741087191 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,724.61 / ETH
Hash:
0xaec6e3848a90fecbdc84cdd3548d74417a30a20a7aa17835c1cf30f53a824fa7
StateRoot:
0x5b027ab6f9b31a6b68dd667c661839853a16029560d6317be8a84a9a5c4cce4c
WithdrawalsRoot:
0x0a26bd59696f0a1b7876dc7a065e1c2c2ec0bf6866ec363214feb8fa11c13812
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5161142712c08bc2b65cb3414ec4bf04f8837deb361f6bb385a84e8c40921475
Parent Root Hash:
0xfcef12619f9b9570c9a8c3b9a21019b5a476d6ca02c14cfb2aaa0bbcdbb6593c
Beacon Chain Deposit Count:
1757515
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xbb4cdd0ed6d77eb5b29742b6492effcc886ec7d1402efd63a015f1b12bd546be
Randao Reveal:
0x95ac272bcab0eec59912de678c4c4b3ef6a5930de8ad59278e2fb5ceb8ed44c241adb728fd2316d6e65e5117fa1d08551730508b5f2207e722d390b7c0e4ecce9a28e25adfa0c9eff96ce7e5fc33b8b4441623fdd47de0dd279561b3b06dd798
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.023855216503774028 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
0.000000004654015607 ETH (4.654015607 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.