Status:
Finalized
Timestamp:
19 days ago (Oct-09-2024 12:33:47 AM +UTC)
Transactions:
190 transactions and 134 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.101745871404986952 ETH (0 + 0.379337487240110213 - 0.277591615835123261)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
82,661 bytes
Gas Used:
19,462,997 (64.88%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000014262531913 ETH (14.262531913 Gwei)
Burnt Fees:
š„ 0.277591615835123261 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,368.44 / ETH
Hash:
0x2fd0b8ab56ca5204a9028241c845e803381bede0ce4a76b4a69814cd0867b34a
StateRoot:
0x4caaf1dac2bc5fffa300515ab2b7e488d8506f9c5590709f41108bd4a36698c4
WithdrawalsRoot:
0xd4ad693027b7ffe50bf3a910822e9b21d6202ce0e8ff023b0895016e3cfa001f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xfb431a204dd8096ff387fc4b9ecd4f101284fa929f6a8ef941d93976e806c5ef
Parent Root Hash:
0xa1acc91d88b90029b53ed05a58124daef8344a5732c5a56513b97603da6340ad
Beacon Chain Deposit Count:
1712148
Slot Graffiti:
prylabs-lido (Hex:0x7072796c6162732d6c69646f0000000000000000000000000000000000000000)
Block Randomness:
0x84d9126adf3e033cbabf3c9dd97011287e40692607cd922290b77b040178377a
Randao Reveal:
0xb7972b607b5cf343c5531a30b474027787b0df9d7eb63af17fc21a9c19e46c51669a394f9352d675765aae23731ce42204ab3d89bbb18625ca4b48865e9cadd1ea9fdc373de09d127e95eb3daad767abcb5ce6a0e9a7de26a8ba2e8516e9fb37
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.084715467342476617 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.