> ## Documentation Index
> Fetch the complete documentation index at: https://learn.breezing.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Explorer Balances Check

> Run an Explorer Balances Check in Breezing to compare recorded token balances against on-chain explorer data and catch mismatches in bulk.

The Explorer Balances Check report compares the balances Breezing has recorded for each token against the balance reported by the blockchain explorer, wallet by wallet. Instead of checking tokens one at a time on Etherscan, you get a full comparison table with the variances highlighted.

### Creating the Report

1. Navigate to **Reports** and click **New Report**.
2. Set the report type to **Explorer Balances Check**.
3. Pick the **Date** to check. For period closes, use the period end date.
4. Select the wallets and tokens to include (use **Select All** for a full sweep), and optionally narrow by chain.
5. Create the report. The results are always separated per wallet, and generation runs in the background.

<Note>
  Bitcoin-family chains (BTC, BCH, LTC, DOGE, DASH) only expose current balances, so those tokens are checked only when your selected date falls within the last 24 hours. For older dates on these chains, verify manually and record it with a [manual attestation](/features/balance-verification).
</Note>

### Reading the Results

Each row is one token on one chain in one wallet:

* **Current Balance**: what Breezing has recorded.
* **Explorer Balance**: what the blockchain explorer reports for that date.
* **Variance**: the difference between the two.
* **Status**: **Matched** when the variance is within tolerance, **Mismatch** when it is not, and **Not checked** when the explorer lookup was not possible for that token.

### When Something Doesn't Match

A mismatch means Breezing's transaction history for that token is incomplete or contains errors, most often a missing date range, an unsupported contract interaction, or duplicates. Work through [Fix Wallet Balances](/features/fix-wallet-balances) on the affected wallet, then **Regenerate** the report to confirm the fix.

This report is also what powers the automated [balance verification](/features/balance-verification) check: running a balance check from a wallet's verification card generates an Explorer Balances Check behind the scenes and records the outcome in the wallet's verification history.