Status:
Finalized
Timestamp:
108 days ago (Aug-03-2024 02:32:59 PM +UTC)
Transactions:
183 transactions and 77 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.01880221564391015 ETH (0 + 0.05628978461387495 - 0.0374875689699648)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
81,599 bytes
Gas Used:
17,200,800 (57.34%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002179408456 ETH (2.179408456 Gwei)
Burnt Fees:
š„ 0.0374875689699648 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,902.09 / ETH
Hash:
0x61d44eecd1165e640c254c4f8cbcda7667818b6f24e904dd6bf51521cc243360
StateRoot:
0x3bcacfbba50b4d21cc2c3d90c1843a485c5b3202044e95278c16d58e3dab99a6
WithdrawalsRoot:
0x7949f41ea2e43f13e11ce161426c03b2550f3aad30b56e0195d7a2ed09e070df
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x6bb300314719b153b9444b27ed8e4958a514f318d8374c6c47faa8e2cc275f11
Parent Root Hash:
0xd3698ce1209582fee3af2f80c009b4e141ee67333ab8c3b4846fe750d5859d3b
Beacon Chain Deposit Count:
1626877
Slot Graffiti:
Nethermind for Lido (Hex:0x4e65746865726d696e6420666f72204c69646f00000000000000000000000000)
Block Randomness:
0x9efea6f02a74ea72578e6c62836f62391c14bffdcebdd53d495da82df88eebfc
Randao Reveal:
0xa533f7e4ea118b25485c32da6d4579ef40645f680a3f27ecc14424a00bd59fc912ef26fd4b571f38ec9c3e826ffa9ab41977d4923429c16b88e4f5645470f0c619dda647eebf8b2ce59f66f2805f396580a40fc3297b2637ef6da8d483f833ce
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.02527147717329898 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.