Status:
Finalized
Timestamp:
10 days ago (Sep-05-2024 07:28:11 PM +UTC)
Transactions:
196 transactions and 165 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.160303391046946437 ETH (0 + 0.234179020583129613 - 0.073875629536183176)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
77,233 bytes
Gas Used:
20,279,948 (67.60%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000003642791862 ETH (3.642791862 Gwei)
Burnt Fees:
š„ 0.073875629536183176 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,367.89 / ETH
Hash:
0xd8b178dce66f09438c25ae44fbf3b09df3613c77b9554b188b5b0aec4d0d5bd7
StateRoot:
0xac6df57734b9c0ab316c7f4e984f5549d8e8a696b636dbeb43e1e28969011f6d
WithdrawalsRoot:
0x7b981f5038ab7b64ef9d82dc92e4e99a15524c1246699e676e9542d3171513fa
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6fec55ee5e73f84e160ba36234267f4758ef034b382bfb3064b976af254ba83e
Parent Root Hash:
0x1973a55becefb36251e314b90e8f72f9a4ab9180d8ac9c4edc59cdfc89ceca51
Beacon Chain Deposit Count:
1672223
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xac75ba13caa5a56d487ec0d0417c16b33759edbf2dd45ee0173bc64779d30c3e
Randao Reveal:
0xb4ed4dbc8b39c673a7d3a9cdb66b7025e89d501ce18a70db14b6906015c27d0040ac00fcf9fc112677a30f2e4843bf530c2557b70b9af4189ee000dd6e11b34c21fdb45c9dada623c6d2e6329c4e85e1e5ced258b3ed8622db18769341269653
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.073973220765997504 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.