Block
#20465972
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
568 days ago (Aug-06-2024 12:33:11 AM +UTC)
Transactions:
226 transactions and 87 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
Block Reward:
0.038483923035871847 ETH (0 + 0.134931922124276965 - 0.096447999088405118)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
99,044 bytes
Gas Used:
23,951,653 (79.84%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000004026778406 ETH (4.026778406 Gwei)
Burnt Fees:
š„ 0.096447999088405118 ETH
Extra Data:
@rsyncbuilder (Hex:0x407273796e636275696c646572)
Ether Price:
$2,462.39 / ETH
Hash:
0x43363d8540c0fd5429923f9943186ba6471fa6b8f23eae4a736eecfcef8f0150
StateRoot:
0x281354896d58915a8c32d8f5dbefbe8f0b7918ec83d13a08decf01aadf55d970
WithdrawalsRoot:
0xb01671dc20364101ad044b7c9b30a64f23b6b76e14034601784e950b351b0d28
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0xd169cfb233fb3e68159ed1d196983e730b98b01b2b84fee1cb9837ff03cbf38a
Parent Root Hash:
0x9f1b7cc8e19a9e441ac3a8ba85de923eb66a4610501639ddd703e697f82ee78e
Beacon Chain Deposit Count:
1627625
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x9acc6fa2854f0ce6e1624b2c3e8fab04881334332ea0f3f3a1c20b5fcc1ffa85
Randao Reveal:
0xb253e630f67970c8126dc3587be727371f287021d1aa9adccea6ca2052603220c2c61dae83ff64104e8bad55be1c224c0afce12ddd1e78732c0daee87092e6ac8d5fa867caa4b616d764d61a907675146cd4703cff77b729c42d7310b4046ee2
Proposer Fee Recipient:
0x388C818CA8B9251b393131C08a736A67ccB19297 (Lido: Execution Layer Rewards Vault)
MEV Reward:
0.099495873670777184 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
640 KiB (5 blobs)
Blob Utilisation:
5 Blobs (83.33%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
655,360 (83.33%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.00000000000065536 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.