Block
#20060626
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
623 days ago (Jun-10-2024 09:45:59 AM +UTC)
Transactions:
142 transactions and 47 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.065035565272141579 ETH (0 + 0.133596293699806535 - 0.068560728427664956)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
61,388 bytes
Gas Used:
14,238,388 (47.46%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004815202987 ETH (4.815202987 Gwei)
Burnt Fees:
š„ 0.068560728427664956 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,665.99 / ETH
Hash:
0xcba785b5c8bc9ceb61c3e1461ee0c77eab0cdc80311f970218107de87ce35b58
StateRoot:
0x1c40b81fa74975195c6202cda51f933a0a36cd2e5a53c1cfa506c764ede7d98a
WithdrawalsRoot:
0x95ae2c4526f53a55861eb59e95a766d444e13e11cee88203aeb14988eb40e3c3
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x12318ea36498cc6601c98b244cc0544b9f2d6675edf6c7a0b990081ace2c0497
Parent Root Hash:
0x0b26459b967e98598ec0e3a27ed91bb16f1fbb3f06c732186db179d98416bcb1
Beacon Chain Deposit Count:
1527109
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x1830366608f2b5bc23ff101c7dcad9ef9c2119fd7608a7b237a108e3a94de8e3
Randao Reveal:
0xa0b39633e301a6e796d321aba694a5f190c84c85b033742ed90f6305ba385946958f76e3684e20e8a6141cdda8804596085161493540378d1d5c737446885b784fd77b453523b3d3a15f14e96250986a97f3b85ec53018098793fd6aaaad7020
Proposer Fee Recipient:
0x51a1449b3B6D635EddeC781cD47a99221712De97 (Fee Recipient: 0x51...e97)
MEV Reward:
0.07507101204401388 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
128 KiB (1 blobs)
Blob Utilisation:
1 Blobs (16.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
131,072 (16.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000131072 ETH
Excess Blob Gas:
1,310,720 (10 blobs)
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.