Block
#20093492
Status:
Finalized
Timestamp:
276 days ago (Jun-15-2024 12:00:35 AM +UTC)
Transactions:
193 transactions and 35 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.021725393291302871 ETH (0 + 0.076869287977702109 - 0.055143894686399238)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
62,580 bytes
Gas Used:
13,261,541 (44.21%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004158181518 ETH (4.158181518 Gwei)
Burnt Fees:
š„ 0.055143894686399238 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,566.61 / ETH
Hash:
0x554b36b89b5e8c51e48c8a6e9af53ee7ab1e76bbb0b40ba0530ab3444471e9cb
StateRoot:
0xcdb8baffdb6edb105c4f85f609832235ec28793c42ba67893984cc6ec48d5464
WithdrawalsRoot:
0x484ada502916e06cd58a1a8c93dada7ee24c9a93472c97e2872143aee78c3318
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x02ef120ba4fd5f4615588e55ce60b078128b36eb96bef7e9945c56c02bb3ec3c
Parent Root Hash:
0x7b0121d99846b0f8a1fba0b7861bd06188668db13a78bb474d4586b06da6c397
Beacon Chain Deposit Count:
1537748
Slot Graffiti:
Legend (Hex:0x4c6567656e640000000000000000000000000000000000000000000000000000)
Block Randomness:
0x4c372799e55fad976a6fb717d770c42fd48a314e21b3d6451b96803fcc828156
Randao Reveal:
0xaef38dab785f4f484b04b99919aef38e69de9131cb1fa8e608b04b8db672a8cdedc83d737cdb7aa418ef515c5cb66152199a2fb5d82fd01f27ad2f8bf4584656cdd1bf78dfbec2b2f58693d55c04e1dfe44c1b308a5bddcfe05b37b2793a9984
Proposer Fee Recipient:
0x8880bb98e7747f73b52a9cfA34DAb9A4A06afA38 (Fee Recipient: 0x888...A38)
MEV Reward:
0.020818127453442797 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.