Status:
Finalized
Timestamp:
15 days ago (Aug-29-2024 06:49:11 AM +UTC)
Transactions:
135 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.00885651515363457 ETH (0 + 0.021222867552942456 - 0.012366352399307886)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
50,150 bytes
Gas Used:
12,100,338 (40.33%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001021984047 ETH (1.021984047 Gwei)
Burnt Fees:
š„ 0.012366352399307886 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,527.97 / ETH
Hash:
0x5190bb4de9bef1a0cce992fffd7db1d24c3d4648e6404e04bcd77b11830a9137
StateRoot:
0x83cbec806618f01949ba92c6474222f2467b8dc159d7f200e2c2a9b0e218dca4
WithdrawalsRoot:
0xe77cb10fdaa47889665cf6533b57ee5c6ac67c8d02ee2e4a5046f69c47adcdd2
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5c60f0ff23e6a58d9c7097629a41f7cd2596b4317449ecf96b952fcbd800f0d0
Parent Root Hash:
0xd6e70e63502e43c7666211734251ed5f70411258c7660232e8fceb04ba3d01a3
Beacon Chain Deposit Count:
1660281
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x766e1e3370a847feae84261c5ff59a73f7b6bb4822f2c37cc37c5371a1562434
Randao Reveal:
0x8cf0499be8a631f7cfa10463e27a02a046e82aac27e216769fa36d7806738daa79230e8780038735db92f8e0a7d0a80b1432c09b6fbebde47a476156ee5e4cf6a41559dbba3a4afd59e4002d2b9255060d439527a72c8d5bac4927afd31d2d02
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.010121157987490139 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.