Status:
Finalized
Timestamp:
170 days ago (Aug-22-2024 10:24:35 AM +UTC)
Transactions:
135 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.041579814930858733 ETH (0 + 0.052721296791363659 - 0.011141481860504926)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
53,976 bytes
Gas Used:
12,040,178 (40.13%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000925358567 ETH (0.925358567 Gwei)
Burnt Fees:
š„ 0.011141481860504926 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,623.57 / ETH
Hash:
0x8434e33578c06a4c87caf396eaca45ddada125ab25cba54447cc849d4f9fcba9
StateRoot:
0x183e38d890f2a3dd8e8fa6395f1860797b13c2b180c02e396ac53a18e45cd608
WithdrawalsRoot:
0x8a8adf747cafe8c5504eefdc36f0e11e334ef3501cf7fa5db558c705bd6bd8b0
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xa918033c02876e4f9457b686cf09d26be759b4c27cc1dcfa1c997ebdcce5bf5a
Parent Root Hash:
0x2321f166169f230adfd611c2d88dd912fb7973f35dc5ff8d57bd851e4e17a592
Beacon Chain Deposit Count:
1650264
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x637bcd6369fb334616d53d1ea7352a5510b58fc3a3a04d009345853a8b5aa000
Randao Reveal:
0xaec9496b0bd94c2631c1f6e97852afde60e60298748d13ca040474d4f1ff6d7c4b44f9e2e2ea295068b7163a2a4942961496fcafcd5c654757fb8e336f0c695c52fd47b39384fb758dfe45f56876206f68be2180e3b41d84728fd779ef416aa6
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.031161576984292436 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 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.