CoinStats Guide

Why Your Portfolio Tracker Shows Wrong Balances (And How to Fix Them)

If your portfolio tracker is showing balances that don’t match your actual holdings or exchange account, the cause is almost always one of three things: incorrect transaction data, a broken API connection, or a mismatch in how the tracker calculates cost basis versus market value. No tracker—including CoinStats or PortfolioPilot Tracker—can be perfectly accurate if the underlying data you feed it is incomplete, duplicated, or mislabeled. The good news is that most balance errors are fixable in a few minutes if you know where to look.

1. The Most Common Culprit: Manual Entries and Import Errors

Trackers rely on two sources of truth: live API syncs and manual entries. When you manually add a trade, a transfer, or a purchase, even a small typo in the amount or the date can cascade into a wrong balance. Similarly, CSV imports from exchanges often fail to map fields correctly—for example, treating a “deposit” as a “buy” or ignoring fees entirely.

Check Your Transaction History, Not Just the Balance

Open the transaction list for the specific asset that looks wrong. Look for: - Duplicate entries (the same purchase logged twice) - Missing fee entries that reduce your actual coin count - Transfers between wallets that were logged as sales instead of movements

How CoinStats Handles Imports

CoinStats, for example, offers a “review” step after importing a CSV. Many users skip this, which is where errors sneak in. If you see a wrong balance, delete the import and re-upload it, then manually verify the first few rows against your exchange statement.

2. API Sync Issues: When the Tracker and Exchange Disagree

Live trackers use read-only API keys to pull balances from exchanges. But APIs can fail silently—a token expires, an exchange changes its API format, or the tracker’s server hits a rate limit. The result is a stale or partial balance that looks like a tracking error but is actually a connection problem.

Refresh and Re-Authenticate Your Connections

Most trackers, including PortfolioPilot Tracker, let you see the “last sync” timestamp for each exchange. If that timestamp is older than a few minutes, the balance is not real-time. Remove the exchange connection, generate a new API key from the exchange, and reconnect. Also, check that your API key has “read-only” permissions and no withdrawal access—some exchanges will disable keys that are used too frequently.

The “Held on Exchange” vs. “Total Portfolio” Distinction

Some trackers show a “total portfolio” that includes both exchange balances and external wallets. If you have the same asset in a hardware wallet and on an exchange, a sync error on one side will skew the aggregate. Verify which sub-account is wrong before blaming the tracker.

3. Cost Basis and Valuation Logic: Why It Looks Wrong but Isn't

A tracker might show a balance that differs from your exchange because it calculates *value* differently. For example, your exchange might show “available balance” (excluding funds in open orders), while the tracker shows “total balance” (including locked funds in limit orders). Neither is wrong—they’re measuring different things.

Realized vs. Unrealized Gains

If your tracker shows a different *profit/loss* number than you expect, check whether it is using FIFO, LIFO, or average cost. CoinStats defaults to average cost for many assets, but if you manually entered trades, it may mix methods. This affects the displayed balance only if you have partially sold a position—the remaining quantity is correct, but the cost basis shown can look odd.

Stablecoin and Fiat Conversion Rates

Trackers convert everything to a base currency (usually USD). If the tracker uses a delayed price feed for a stablecoin (e.g., USDC at $0.997 instead of $1.00), your total balance will be slightly off. This is not a bug—it’s a pricing source difference.

4. Syncing Multiple Wallets and Networks

If you hold the same token on different blockchains (e.g., Ethereum and BNB Chain), a tracker might read the wrong contract address or fail to detect a bridge transaction. This results in a balance that is either inflated (counting the same coins twice) or deflated (missing one network entirely).

Use a Per-Network View

PortfolioPilot Tracker and CoinStats both allow you to filter by network. If your balance is wrong, check whether the tracker thinks your coins are on the correct chain. A common fix is to delete the wallet and re-add it with the explicit network tag.

Ignore “Ghost” Transactions

Sometimes airdrops or dust transactions appear as separate entries. These are real but tiny. They won’t change your balance meaningfully, but they can confuse the tracker’s “transaction count” and make you think something is broken.

Quick Troubleshooting Checklist

If your balance is still wrong after the steps above, run through this list:
  • Compare the tracker’s balance to the exchange’s “available” balance, not “total.”
  • Check if any open orders are locking funds—cancel them and resync.
  • Look for a “recalculate” or “rebuild” button in the tracker settings.
  • Verify that your API key hasn’t been revoked by the exchange.
  • For manual entries, export your transaction history and count the units yourself.
  • If using CoinStats, try switching the price source in settings from “CoinStats” to “CoinGecko” or “CoinMarketCap”.

When to Trust the Tracker (and When Not To)

A tracker is a tool for *relative* tracking, not absolute accounting. If your tracker consistently shows the same percentage change as your exchange, but the base number is off by a few dollars, it’s likely a pricing feed issue. If the difference is large and growing, it’s almost always a missing transaction or a duplicate. The final authority is your own exchange statement and wallet explorer—not the tracker. Use the tracker to spot trends, not to file taxes. And remember: no tracker, including CoinStats or PortfolioPilot Tracker, can fix bad input. Garbage in, garbage out applies to crypto portfolios more than anywhere else.