Block
#20502616
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
576 days ago (Aug-11-2024 03:14:11 AM +UTC)
Transactions:
88 transactions and 41 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.009859053343169525 ETH (0 + 0.018311940212664169 - 0.008452886869494644)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
37,162 bytes
Gas Used:
10,011,724 (33.37%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000844298831 ETH (0.844298831 Gwei)
Burnt Fees:
🔥 0.008452886869494644 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,555.67 / ETH
Hash:
0xafb58568ad8a7cf5274f6cd36e0b9aa52ee869fa4a1c3c8f7176b5215d8b97f3
StateRoot:
0x4ec17dc5e0578c607262e1752af324b8ed06531264d3e89e245a33a61f703436
WithdrawalsRoot:
0xe7043dc585725624e07953ac37cec78bc6074be754a916b32d78c50e7af89227
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xae8fa266b02e7b6963768b9e7bcbaa8a32fb5145e6ca644abb98dd7766becba6
Parent Root Hash:
0x26f52e5d7445a59f5185cf328c07d4e8932217f27e9cc8c472ee2d86a93cc739
Beacon Chain Deposit Count:
1633629
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xb0dcc2c763e6e76c538c5b26c2e48ee707181bac18d82c727bcc5abcbd443738
Randao Reveal:
0x8be5a87dd722f88cf8c5a8c9820cec31cda5a24e9d4f4ba4861826541f0db6098ab3a93eae1a4870e1911f7bab4948f619cb822505ae0376d60c1db25e109d59dced1f1a77e8d79bf679d6d41524687ba7d5f7f330ff32ffdf8c556d6fce83f9
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.013862381736151606 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (66.67%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (66.67%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000524288 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.