Block
#22686308
MEV Block
EigenPhi
Status:
Finalized
Timestamp:
256 days ago (Jun-12-2025 05:10:59 AM +UTC)
Transactions:
160 transactions and 71 contract internal transactions in this block
Withdrawals:
16 withdrawals in this block
Fee Recipient:
beaverbuild in 12 secs
Block Reward:
0.014095903510811149 ETH (0 + 0.030292739596118623 - 0.016196836085307474)
Total Difficulty:
0
Size:
79,701 bytes
Gas Used:
17,408,009 (48.36%)
Gas Limit:
35,999,965
Base Fee Per Gas:
0.000000000930424386 ETH (0.930424386 Gwei)
Burnt Fees:
š„ 0.016196836085307474 ETH
Extra Data:
beaverbuild.org (Hex:0x6265617665726275696c642e6f7267)
Ether Price:
$2,644.51 / ETH
Hash:
0xb35c83f1339894293522a40b8ee6d14424d0d116c64f898643fb1bf3d5e133b9
StateRoot:
0xf5a066e5944a1a43b87614976765acb2e23be65e87eb79b0f5d1973632e98558
WithdrawalsRoot:
0x8ac206a21e4cfdafa1abac52c36117098c983efaad45ea08d6969a1257459ec1
Nonce:
0x0000000000000000
Slot:
Epoch:
Proposer Index:
Slot Root Hash:
0x5fc67685601d429adfbf60832e27a5a74488ffa785a7a8b8e311ca4c09753e57
Parent Root Hash:
0x39e145908b334463ca6c475137d42f5c63c3cd40ed146d557a8cacc0951affe8
Beacon Chain Deposit Count:
2045305
Slot Graffiti:
0x (Hex:Null)
Block Randomness:
0x11296b7beded5620d46b7a8d404b6c38ab5a77a69cfdeaa6f3f1c193d673ddd4
Randao Reveal:
0x983e5d758eca0349939e1bab37dd72bf09471a5afda9949815808f7ade713b4a3f527d24c5c6e62f11cd1ee3e8fa447e1798c678aa53145eca96d9775bf219424ff27fd86cf1087849badf7e375fadbf645305dad8c1646e4bd5b6e87b1359e4
Proposer Fee Recipient:
0xADaE1798F761Fa7fce29B6673D453d1a48A2931A (Fee Recipient: 0xADa...31A)
MEV Reward:
0.031805863282661897 ETH
MEV Payout Txn Hash:
Blob Tx:
Blob Size:
512 KiB (4 blobs)
Blob Utilisation:
4 Blobs (44.44%)
Blob Gas Price:
1 wei (0.000000001 Gwei)
Blob Gas Used:
524,288 (44.44%)
Blob Gas Limit:
1,179,648
Total Blob Fees:
0.000000000000524288 ETH
Excess Blob Gas:
262,144 (2 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.