Block
#20062275
Status:
Finalized
Timestamp:
222 days ago (Jun-10-2024 03:18:11 PM +UTC)
Transactions:
166 transactions and 88 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.052537870214389098 ETH (0 + 0.304178368138165908 - 0.25164049792377681)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
74,031 bytes
Gas Used:
15,345,058 (51.15%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000016398797445 ETH (16.398797445 Gwei)
Burnt Fees:
š„ 0.25164049792377681 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,665.99 / ETH
Hash:
0xe73a67516bc0715d66e5dd6194664ae1d33125b254d4ff42689e11ee9cb6089c
StateRoot:
0xb271032fba8ae555e689ef3755e36f80e1d09e3d0284ee0c6c5a31372bcddbfd
WithdrawalsRoot:
0x884410d7a72230040a1d240a9a68558a0d002fedb0da793754134451f5300db2
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x1e68670041535a0706a9944535d904ebce3125effd4b09075ebd42da8f765dfe
Parent Root Hash:
0xac410670f7a7dda936caa2d962c5f885e3aab898f985861bdb5b59d683f55ee4
Beacon Chain Deposit Count:
1527435
Slot Graffiti:
Lido ā”ļøAllnodes TKcdcb (Hex:0x4c69646f20e29aa1efb88f416c6c6e6f64657320544b63646362000000000000)
Block Randomness:
0xa2ad1447968e27df56370909dd06bfd17ed1467659d07300a0243fcd30f3d213
Randao Reveal:
0x87998fb8804c25e27258c1f8524a6582a204ac36bb58dc3313d86bff4dfadfdc3a2db30bb1fb61384bd81cb2ec132d4a159ef60d78baa48714cf1cd3009dd4b2b57833254cfe892e81809a2e31d1636136ba335b00a06e1515970af8b9f44f4d
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.158705627245259168 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.