Block
#16039358
Status:
Finalized
Timestamp:
1449 days ago
Proposed On:
Block proposed on slot 5205257, epoch 162664
Transactions:
159 transactions and 35 contract internal transactions in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.028026671536469986 ETH (0 + 0.143802416755230046 - 0.11577574521876006)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
70,118 bytes
Transaction Actions: Beta
Gas Used:
11,032,308 (36.77%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000010494245195 ETH (10.494245195 Gwei)
Burnt Fees:
🔥 0.11577574521876006 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$1,202.96 / ETH
Hash:
0x1ccd7c322c9e3e7bbed7586a5597e7814ec1b2ad53f68f7afa68a421f445245f
StateRoot:
0x5303c42770a2c4a1cae58bc0080394c08154f75c92d6870754f5a883b6dbe0e6
Nonce:
0x0000000000000000
Slot:
5205257
Epoch:
162664
Proposer Index:
453138
Slot Root Hash:
0x3fed75215d1eb284dce477413013f1cd351460c9f9df7ee6b0ededa006023175
Parent Root Hash:
0x0e4683de7731a64717e013ddaa958fa19ddacc5d3d621f5aa528afb3a116969f
Beacon Chain Deposit Count:
489027
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xd0f097629ec67b3c33144c9cf72140d6be54ea4b47cdd93c38b6da72beecc3ef
Randao Reveal:
0xb96c557a634d0b01eccd719d945ae4766a22961f1f2db50048d75963093fc596d9013c51adb77493ad573b7b793832d0105c2867f403fab60e29261b8c19cbd10b5357a4aecca275eb8e17a802df809b3c13a794fbe489bc4eb61f4749f673fd
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.027711844180619986 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
Total Blob Fees:
Excess Blob Gas:
Reserve Blob Base Fee:
| Rank | Participants | Txn Count | % Gas Used | Txn Fee (USD) |
|---|
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.