Track crypto across several exchanges and wallets in one place
To track crypto across multiple exchanges you keep one canonical amount per coin, not one line per venue, and you update both sides of a transfer in the same sitting. Bitcoin.org gives 6 confirmations as its minimum recommendation for high-value transfers, and that waiting period is where double counting is usually created.
Key takeaways
- Inventory the venues before the coins. Two exchanges, a browser wallet, a phone wallet, a hardware wallet and one dormant platform is six places, and the forgotten one is what makes a total wrong.
- One row per coin, summed across venues. Three BTC rows in a tracker is how one gets updated and the others go stale.
- Round to a single precision everywhere — five decimals for BTC, two for a stablecoin — or the total drifts for no visible reason.
- Update both sides of a transfer after it confirms. Bitcoin.org lists 6 confirmations as the minimum recommendation for high-value transfers and states that a Bitcoin transaction cannot be reversed, only refunded by the recipient.
- A consolidated total is a snapshot of quantities and prices. It is not a transaction history, not a cost basis record and not a tax report.
Coins spread over two exchanges, a phone wallet and a hardware wallet are still a single position in each asset, and the total you care about is the sum across all four places. The work is bookkeeping: write down where everything lives, add up each coin once, and re-check on a fixed day.
The failure this prevents is double counting, which almost always happens during a transfer. This page sets out an inventory, a review routine, a rule for coins in transit, and the three mistakes that produce a total nobody trusts. It is information about record-keeping, not financial advice.
Start with an inventory of venues, not of coins
Write down every place that holds something, before you write down any amounts. Most people underestimate the count: two centralized accounts, a browser wallet, a phone wallet, a hardware wallet and a small balance left on a platform used once in 2023 is six venues, and the forgotten sixth is the one that makes a total wrong.
| Venue | What it holds | How you read the balance |
|---|---|---|
| Exchange A | BTC, ETH | Account page, after login |
| Exchange B | SOL | Account page, after login |
| Phone wallet | ETH, USDC | Wallet app home screen |
| Hardware wallet | BTC | Companion app in watch-only mode, or a block explorer |
| Old platform | Small BNB balance | Login, quarterly |
Keep this list somewhere that is not a shared document, and keep it short. It exists so that a review has a defined end: you have checked every row, so you are done.
Collapse the venues into one amount per coin
Once the inventory exists, the tracking is addition. If exchange A holds 0.12 BTC and the hardware wallet holds 0.31 BTC, the record says BTC 0.43 — a single line. The venue breakdown lives in the inventory table, not in the tracker.
Two rules keep the numbers honest:
- One row per coin, never per venue. A tracker with three BTC lines invites the mistake where one is updated and the others are not.
- Round consistently, in one direction. Pick a precision — five decimals for BTC, two for a stablecoin — and use it everywhere. Rounding up in one venue and down in another produces a total that drifts for no visible reason.
Reading a cold storage balance without plugging anything in is its own small problem, worked through in tracking a hardware wallet balance without connecting it. Manual entry has an obvious cost here: you re-add the numbers yourself instead of an API doing it. It also has a specific benefit, which is that no read-only key and no public address is registered anywhere on your behalf. That trade-off is set out in full in the comparison of address, exchange key and manual entry.
A review routine that takes about five minutes
Pick a day and keep it. Sunday evening, the first of the month, whatever survives contact with your actual week. The routine:
- Open the inventory list. Work down it in order, never from memory.
- Read each venue's balance and note it.
- Add each coin across venues to a single figure.
- Update only the coins that changed. Most weeks, that is none of them.
- Compare the new total with last time. An unexplained move is a prompt to look again, not to accept the new number.
Step 5 is the one that catches errors. A total that jumped 20% with no purchase and no market move is usually a decimal point, not a windfall.
Coins in transit: the rule that prevents double counting
A transfer between two venues you control does not change what you own. The total before it and the total after it should be identical, and if your record says otherwise, the record is wrong.
Double counting happens in the gap. You send 0.2 BTC from an exchange to a hardware wallet, add 0.2 BTC to the hardware wallet line while the transaction is still confirming, and the exchange line has not been reduced yet — so the tracker briefly shows 0.2 BTC that does not exist. Waiting for confirmations is not paranoia: bitcoin.org's own guidance lists six confirmations as the "minimum recommendation for high-value bitcoin transfers", and states plainly that a Bitcoin transaction cannot be reversed, only refunded by the recipient (Some things you need to know).
The rule to follow: update both sides of a transfer in the same sitting, after the transaction has confirmed, and never one side at a time. If you are interrupted, do nothing until you can do both.
What this routine does not solve
A consolidated total is a snapshot of quantities and current prices. It is not a transaction history, not a cost basis record and not a tax report; those need a dated log of every purchase, sale and fee, which a phone tracker is not keeping for you. The routine also does nothing about custody risk — a balance shown on an exchange account is a claim on that company, and the number in your tracker is unchanged by whether the company is solvent.
Holdtotal fits this routine as the place the summed figures live: you type one amount per coin, and it prices that list from a catalogue covering the top 250 cryptocurrencies by market capitalization plus Layer 2 and Bittensor subnet tokens, with a resizable home screen widget showing the total without opening the app. Holdings are stored on the phone, and no Holdtotal server receives them, though Android Auto Backup may copy app data to your Google account unless backup is switched off (Back up user data with Auto Backup). It connects to nothing, which is precisely why the inventory list matters — the app cannot notice a venue you forgot. Anything asking for a recovery phrase to "import your balances" is a theft attempt, as covered in why no tracker needs your seed phrase, and what a tracker transmits is set out in what a crypto tracker app sends off your phone.
FAQ
How do I avoid double counting when moving coins between wallets?
Update both sides of the transfer in one sitting, after the transaction confirms. Subtract from the sending venue and add to the receiving venue at the same moment, so the total never changes. Bitcoin.org lists six confirmations as the minimum recommendation for high-value transfers, which is a sensible point to wait for. If you cannot do both sides now, change nothing and come back later.
Should I keep a separate line for each exchange?
Keep the venue breakdown in your inventory list and a single line per coin in the tracker. Three BTC rows in one tracker is how one row gets updated and the others go stale. The exception is if you genuinely need per-venue exposure figures, in which case a spreadsheet with a venue column handles it better than a phone app, because a sheet can sum and group at the same time.
How often should I check balances across all my accounts?
A fixed day beats frequency. Weekly is enough for most people, monthly is fine if you rarely move anything, and quarterly is the floor for dormant venues holding small balances. What matters is that the review follows a written inventory rather than memory, because the venue you forget is the one that makes the total wrong.