Block
#20454269
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
540 days ago (Aug-04-2024 09:23:23 AM +UTC)
Transactions:
224 transactions and 60 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.044688260845765964 ETH (0 + 0.062690733732888632 - 0.018002472887122668)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
78,679 bytes
Gas Used:
17,748,933 (59.16%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000001014284796 ETH (1.014284796 Gwei)
Burnt Fees:
š„ 0.018002472887122668 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,688.08 / ETH
Hash:
0x328472ef86c2d0f84268f0f150d1e66f2ea6698fbb3bfc585ccf9101efa9b7e0
StateRoot:
0x90363fcc0f59ac91969c60b10504c011304ebef16ce64e381656404a705c9118
WithdrawalsRoot:
0xe41d5500c13ca8fa583a11d0d26a371bd3f6213ce92b612395f262218822dce7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xf9d9eebadb495ed5595f3546a23a09cc6a22edc057be1346db2f79aa1b79a615
Parent Root Hash:
0xd74fed17951abd828c9f2c98124dfa8b33da4092ae3b8b6974ea6713e746df03
Beacon Chain Deposit Count:
1627036
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x7a4de206f0b681417c6ab4f0cb0906def54fe74a217216b92a797438eda22756
Randao Reveal:
0x96f146043a97021417720c2d24c1688c0e79cbbde0fcd6eb21ed6895567044261d8c78767882850e5598b6bebc57041604426e499398ac2cb33b5f1c909527fbe6c14e26bb0ec146474f77f2112ce59795c0e87f31eeffe9dd9e01cb6be06820
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.24377499969591028 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:
0 (0 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.