Status:
Finalized
Timestamp:
25 days ago (Aug-17-2024 08:54:47 PM +UTC)
Transactions:
88 transactions and 34 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.021985642362805714 ETH (0 + 0.030572315031430764 - 0.00858667266862505)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
49,926 bytes
Gas Used:
10,053,305 (33.51%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000085411441 ETH (0.85411441 Gwei)
Burnt Fees:
š„ 0.00858667266862505 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,614.92 / ETH
Hash:
0xd3f3551af118676f0ba1cafe034756e86e9e283d6b9f38bb8bc587be43125b6e
StateRoot:
0xc79e4183702ed9a8cff7c0db58a0a1689c9dc9f30cd2e2feff5f0cae9441b97b
WithdrawalsRoot:
0x223d3345fc4b75a8be25a4f58dea31a15fbcb4da9de846a807246ef8f7ab9f2f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc195abba3b3d91728aadaa9f422aacc0f5b7ff53d1c7fb1c9fc3e5be17c1a994
Parent Root Hash:
0x83a32bba6ba187f75c373b92dbb3e47aff58a0c02f6fe2bd40424283a0291dcb
Beacon Chain Deposit Count:
1645142
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x0956f711fddc396b5fa299883a5a21694b835bd48f6d56e7387dfbdbfe21911f
Randao Reveal:
0xa49361ff6bde1d61dd313bf60e5c02db410ad40839a7e78fd206edaff8e20eceef3e1953a1e747d46eff9ee57bf1374f0881075a274cc60d325fc01d2cbe2349701c2c38dddfb94decb46c3138c127f9a2c2c71ef21b8c42f6d1053c80766c5c
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.023933964966798213 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
384 KiB (3 blobs)
Blob Utilisation:
3.00 Blobs (50.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
393,216 (50.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.