Block
#0xdf52b76d30e59640ac1280c0c24fae9cecf815a1f8911d71b81c6b8cca5a4f21
Status:
Finalized
Timestamp:
126 days ago (Sep-22-2024 09:09:47 PM +UTC)
Transactions:
139 transactions and 50 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.038483892414081028 ETH (0 + 0.118471613885250952 - 0.079987721471169924)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
47,698 bytes
Gas Used:
11,174,983 (37.25%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000007157748828 ETH (7.157748828 Gwei)
Burnt Fees:
š„ 0.079987721471169924 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,581.43 / ETH
Hash:
0xdf52b76d30e59640ac1280c0c24fae9cecf815a1f8911d71b81c6b8cca5a4f21
StateRoot:
0x704e2de6fa47426c04610dc458408997b1efe8d2e25a58668ed0ba095ee6c1f3
WithdrawalsRoot:
0x22ce310c1119b2afeba05dfb61f75748a5bef0cadd81c1243ec5867d57fb082c
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x454c62d28dbe3bfd2a4080c899b32b128970aaa834ada38f277a7d94df0a1305
Parent Root Hash:
0xdae66c4fafe48a7d3232bbe161b232c69bef14b0f3e2ff7299c602183cb5d103
Beacon Chain Deposit Count:
1688896
Slot Graffiti:
Block by Stakely.io Lido101 (Hex:0x426c6f636b206279205374616b656c792e696f204c69646f3130310000000000)
Block Randomness:
0xde7e47d2135f77465705c3f9001447b97eae235c06094f533d74aeef4fa8c2fb
Randao Reveal:
0x87d65931c6993a7344f0ba01c905fa9cc1c34ea94bdd35aa8c658eef181043ae213ccc718d85547e3d82cf68f23c086314f8a1e71690d80f3ee0ee20a30574e950c86377c9e7e40de6b3dba2bc2e98ce94d0143694fc1f672896b16a47545ed2
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.031050227023688745 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
Blob Utilisation:
Blob Gas Price:
Blob Gas Used:
Blob Gas Limit:
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.