Block
#20187703
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
626 days ago ()
Transactions:
92 transactions and 51 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.030784531226653723 ETH (0 + 0.066270050102407331 - 0.035485518875753608)
Total Difficulty:
58,750,003,716,598,352,816,469
Size:
48,948 bytes
Gas Used:
11,328,406 (37.76%)
Gas Limit:
30,000,000
Base Fee Per Gas:
0.000000003132437068 ETH (3.132437068 Gwei)
Burnt Fees:
🔥 0.035485518875753608 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$3,373.80 / ETH
Hash:
0xf3ee60c371bd90f535ac6c1d28401f07f2b4af577728fd2024ee1b1e7f3a1252
StateRoot:
0x0f602cb7aba54b354d06d64d4397e62a9311e8180fe14cb20e83cd76f8c4832c
WithdrawalsRoot:
0x5c3454633638bc2cfb5ba7bac56e9438839aed523fae1f32565aae5e15ac3c53
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x58f6fd98381613777324a1af2269082094d5471beb37f59e655ad99d63c63b1a
Parent Root Hash:
0x49b3d201458d064d5dedff893fa8ff74babe356e04925dc2edbc80bd260df8de
Beacon Chain Deposit Count:
1561378
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0xd01acc1e09eb781df6878ca70ea0d6b37ec3dbb9ddca77778779579702721050
Randao Reveal:
0xaa413831234ab724869898d2dc2c5e4c9a2bd438d7170f418e408d9f87225eda31e9676be51c1b17a6ab3098457e1dd8167c6e13978cf0c610ec1836ba8aa29e16e2120ff8eb4cffd8f122fee86e782e53ff6ba7ddbb1fdef25eaf94254617ab
Proposer Fee Recipient:
0x518489F9ed41Fc35BCD23407C484F31897067ff0 (Fee Recipient: 0x5184...ff0)
MEV Reward:
0.038055746718517733 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
768 KiB (6 blobs)
Blob Utilisation:
6 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
786,432 (100.00%)
Blob Gas Limit:
786,432
Total Blob Fees:
0.000000000000786432 ETH
Excess Blob Gas:
786,432 (6 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.