Block
#20632006
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
552 days ago (Aug-29-2024 04:58:11 AM +UTC)
Transactions:
169 transactions and 109 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.016793852589516498 ETH (0 + 0.029810399786373543 - 0.013016547196857045)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
90,851 bytes
Gas Used:
17,145,561 (57.15%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000759178845 ETH (0.759178845 Gwei)
Burnt Fees:
🔥 0.013016547196857045 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,527.97 / ETH
Hash:
0x99ecf80a0ddfcb885cabda677a0d96c502c157dabae7ed044eaa232bb2923f5a
StateRoot:
0x1d4799520ad51e21f118bfb172808a87cedfa9afe132ee9dc9b05f9f6c19b357
WithdrawalsRoot:
0xf5f3fa15d2b3756b6aaa78161f0f4731ab5a6782f14fd45ea09544e806dca7ec
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xc494eeba01e001dffe8483f0b8c149bd9f1a9ffdf880439eaab977d205c53f8e
Parent Root Hash:
0xab5c6c3d2883300b2d78feb978d5e9ade218b3e3235e2e85c0b3ce80fe44387a
Beacon Chain Deposit Count:
1659447
Slot Graffiti:
C0D3 1S SP33CH (Hex:0x4330443320315320535033334348000000000000000000000000000000000000)
Block Randomness:
0x2e096c872609f402f4d7e5f069c493ddea1626684f36698225eef3cd0997a79e
Randao Reveal:
0xb6ff869259d1a21752b4f712727a55a80516630a457186217262855e61f6eb6f0d31d62f8bfadaa316df5461d2801d5f1809ad9935fe1b0c1d2bb41ca2f8688ca8dd8646c6e7fda3551ca7ffbba46c06daac03ce7d2a06da3c00215b306691df
Proposer Fee Recipient:
MEV Reward:
0.020757772377934049 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
256 KiB (2 blobs)
Blob Utilisation:
2 Blobs (33.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
262,144 (33.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000262144 ETH
Excess Blob Gas:
131,072 (1 blob)
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.