Status:
Finalized
Timestamp:
236 days ago (Aug-04-2024 09:04:47 AM +UTC)
Transactions:
241 transactions and 81 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.017767661404408982 ETH (0 + 0.041866132998350486 - 0.024098471593941504)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
82,902 bytes
Gas Used:
19,599,744 (65.33%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001229529916 ETH (1.229529916 Gwei)
Burnt Fees:
š„ 0.024098471593941504 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,688.08 / ETH
Hash:
0xd4f2efe01fb843416e3a53c811c1c2d36e2cfa3fce55e95cb7b4aa36404f55f4
StateRoot:
0x97e1c4ce2bcc18a5e8e380bac769725ee67134b37ba697c2601974d8361d2c5b
WithdrawalsRoot:
0x94418a35c989be19a6c1da9de50739be0a3169facc100821970f5b441b668e4f
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc26868ab34490be588cb61e6128baa45eeac75a31dee2d336e07625b166e70c9
Parent Root Hash:
0x62ee59db36d30f08a977cafd8803ae6ff6beac62b27a9670da6dfa2e11b538c3
Beacon Chain Deposit Count:
1627036
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0xa530086fb99cb308d7e1efbd76ef7bb4c5d90f5f212f864a3108e394b6d97224
Randao Reveal:
0xa1a5a5bf5fc3f08cced0d50ee10833e46e15869e1fc7e96be99a804367623c0557b2718d7d01d47b5f9002ecdb3cf20e10a5a8c0d5eb5fc88a51ac65e04da50c9b7554f4bc08864d6873dde40ed3a3d7fcc4fafc69485ab8f66f568cad3bf476
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.018999588592119816 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.