Block
#22674432
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
236 days ago (Jun-10-2025 01:22:23 PM +UTC)
Transactions:
167 transactions and 93 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.02407386100838329 ETH (0 + 0.127241159979430006 - 0.103167298971046716)
Total Difficulty:
0
Size:
88,952 bytes
Gas Used:
15,648,618 (43.47%)
Gas Limit:
36,000,000
Base Fee Per Gas:
0.000000006592741862 ETH (6.592741862 Gwei)
Burnt Fees:
š„ 0.103167298971046716 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,816.15 / ETH
Hash:
0x72264792178a0c2a2d6df5bd962f807d53b43a7776ba05965b0bfb66fb5c2fb3
StateRoot:
0xb83834913ea372610c935a520ae2fed393641a29ff5f407d7cd6a8c89dd2fc17
WithdrawalsRoot:
0x20c4e4f4857e3e0b054f9ac9450edf7771b6c75b4278a6cfaaf73827f80417d7
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x643784ec4f34e0a4abb2e1e452b8b6506a0b3c8a98c171dd2ae9814ed07fa7d4
Parent Root Hash:
0xca0684036b093c2d58b87ba2b493bdf22c61fc78a81ed2a66e55ff581dfc7fef
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x741dd0f2d1b1f9cc7752d74a2a142dae1b8b58f21946bb7659de0bdd603f687b
Randao Reveal:
0x930667d75722d2c9fd202562ec0fbab0d49d8db96b6da2f41d901a1c750de7eb383aa38e37bfa4965cdecd9ff54576140b2f7945f803333db2e8c8df32de8d45aff1c66f2ac6e8707f8c6b0896779c36050cdf4b04fbac2dc3e0672170c6dc31
Proposer Fee Recipient:
0xBB3AFDe35eB9f5FeB5377485a3bD18a3EB0FE248 (Fee Recipient: 0xbb3a...248)
MEV Reward:
0.026065425286184173 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
1.125 MiB (9 blobs)
Blob Utilisation:
9 Blobs (100.00%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
1,179,648 (100.00%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000001179648 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.