Status:
Finalized
Timestamp:
143 days ago (Aug-10-2024 12:03:59 PM +UTC)
Transactions:
127 transactions and 62 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.071325731325811103 ETH (0 + 0.094333625596754667 - 0.023007894270943564)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
65,615 bytes
Gas Used:
13,877,246 (46.26%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001657958234 ETH (1.657958234 Gwei)
Burnt Fees:
š„ 0.023007894270943564 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,610.64 / ETH
Hash:
0x1268cfa7d6e05ae3957e98e955c155c9b6eb35d537807d731c4093913b23fc12
StateRoot:
0xb141f9603c08ae71c4b7e854048f792c927df30950bb829f252ef78c036900ca
WithdrawalsRoot:
0xff57ef4e85902680ac8698ba658caf2b3414c2232b90637b321cceec06c28318
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1d374e2a688fc18caae2722aee542d48ae107bb4fd36b9ed906056fd24613cc4
Parent Root Hash:
0x7542e1789eb9cad9a1c5847e6fe01ac235c08137e3fb59c771fe233974c71aee
Beacon Chain Deposit Count:
1633262
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x1f9514427ac1d41b77d89b95801c2ef8bb8f9f79a364af9596ab6ea62a9268fe
Randao Reveal:
0xb7fadd668b5fc851a9b7ac3a434a3d542c8a765fb2cec5e35f243eb88c5266656d3b43cd305f0415813bc62b5e0fd6cb01abb6c22bec50315b6a848c5851ce63c8a26a5c94c78d11717384b323f42988a9aa58978c8a52aa3290ec8a1f892137
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.044314435083969886 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4.00 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.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.