Block
#20174477
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
608 days ago (Jun-26-2024 07:49:59 AM +UTC)
Transactions:
162 transactions and 50 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.011045306462212998 ETH (0 + 0.041472566340063121 - 0.030427259877850123)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
73,288 bytes
Gas Used:
15,028,967 (50.10%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000002024574269 ETH (2.024574269 Gwei)
Burnt Fees:
š„ 0.030427259877850123 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$3,369.46 / ETH
Hash:
0x583fe5b215da80aa4446cee0e820019fdc4ae7f199df5e1d29cc9fec63b31bd6
StateRoot:
0x4b25714cfcff7788cfedc7c60089aa3c449f3ab9cd71561e23c1576654726c76
WithdrawalsRoot:
0x2a8e7141736c3e2d8bb03a154bbdc8f8f3bd550055d3dc24c480a72a40d68844
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd15222ae5184e7f9e92aec9752d5a2e317086d7f02e173a35baf5cc0ad7870d4
Parent Root Hash:
0x0f7b769ea5a0bf6865ec842e2099741aa79733162bd81ef9985916185b326a0e
Beacon Chain Deposit Count:
1558837
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x63e4f0be089daf4c566b31419a6d84e2772697359fd08832e5aee059ecdf25b9
Randao Reveal:
0x8210c12689c9726d23b9f96601c58d3e0754fb17ca554ac917faf62a2b1f419fd4b7a0cf496e5a22775a70eed8e32cc1154aea9f0b577f2ade607be19353494dd8c9dbb81f52789f547b5e781bf9ad6a27197f899beb3e76031008b3ee28af37
Proposer Fee Recipient:
0xa27CEF8aF2B6575903b676e5644657FAe96F491F (Fee Recipient: 0xa2...91F)
MEV Reward:
0.020190852597365546 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,572,864 (12 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.