Block
#20349176
Status:
Finalized
Timestamp:
95 days ago (Jul-20-2024 05:16:35 PM +UTC)
Transactions:
172 transactions and 76 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.029975486624923355 ETH (0 + 0.086053407577362325 - 0.05607792095243897)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
60,797 bytes
Gas Used:
15,805,529 (52.69%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.00000000354799393 ETH (3.54799393 Gwei)
Burnt Fees:
š„ 0.05607792095243897 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,518.85 / ETH
Hash:
0x81ab37525204a613d98054acab17cbbb7727375c3f9acc1f95cf9f22b2654642
StateRoot:
0xa054767b40393f102475dc7dab9fcb8b0576992966ee121d18d087cd09fe108a
WithdrawalsRoot:
0x87dcc8cbcd3e28464fb62f10dfd5f72f053da2aadef74e5818b81f55c6591694
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf00d54238e4425b9e8ddf8afdeab96b960f0c5340f8de48b24db52669dc32db8
Parent Root Hash:
0xb5b8ce7afa6931843fe5041e296fe6e3549461375f37939f07a4ff29f56be4e0
Beacon Chain Deposit Count:
1597418
Slot Graffiti:
Block by Stakely Lido009 TKNM (Hex:0x426c6f636b206279205374616b656c79204c69646f30303920544b4e4d000000)
Block Randomness:
0x4872dbd77fc5d8781a65fb4643c2494f8eca911601e1d0983f4756e0d3ad8e52
Randao Reveal:
0x85408254b117ab54ee1456983b07e8251cdaed7d6bad3f6d34c2f61732dc12cc501469738bfce5f43ccf4c88f276ec4a0bb99e71376f0a60c5b5f41a999568dc78a21028b48e2c9205f812370ef99f01ae183f85dc14d39b7bfb09d76b05cb99
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.228513989593833513 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6.00 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.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.