Block
#20604269
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
549 days ago (Aug-25-2024 07:59:23 AM +UTC)
Transactions:
93 transactions and 26 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.008008539761926627 ETH (0 + 0.014722667811607104 - 0.006714128049680477)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
32,139 bytes
Gas Used:
7,136,119 (23.79%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000000940865483 ETH (0.940865483 Gwei)
Burnt Fees:
š„ 0.006714128049680477 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,747.52 / ETH
Hash:
0xb0b884460e8f48dbc7b140e2c61fc7075b39063c9301baac00fdf6b28c63efbf
StateRoot:
0xd21ff47bb69c1fc0567c9d4610cbd2b190b883fa87dd72d751b9405a87c1d7fb
WithdrawalsRoot:
0x20c30aabef0c18c3d9378030ee1a3cf064c836e30064db1fba9af729891f711e
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x154905908252876d00860381b441f3a8ed54dd82e0ffcfd85288a68fd4338a8b
Parent Root Hash:
0xd60a46fee899accfb0c29c432607c69bb5fc0d16f998531831286d698fa3f810
Beacon Chain Deposit Count:
1652648
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x55e661bd96f42e6804ad10122ce22743024fb13e99ac0439f8e3275f3d7211ff
Randao Reveal:
0xb2d1b4f63a81321038e47b5b6dc1a31d13b572be9f87160a18a3701fbc487bb45ccca887cda0d13e3cac4e2ed31c44e61969321c83ef6780593b0ae4571da2f83f75a5cbf78ebbdd72280c170184d8e05498145aa6c2df56fc8d87302c25cf1e
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.014974538061912478 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.