Bitcoin balance: confirmed, pending and available are different

A confirmed Bitcoin address balance, a pending balance and your wallet’s available balance can all be different. A confirmed-only view follows transactions already in blocks. Your wallet may also account for unconfirmed spending and change across several addresses. Compare the scope and transaction state before treating any displayed total as money you can send.

This guide covers ordinary Bitcoin Mainnet on-chain payments. It does not cover Lightning, wrapped BTC or an exchange’s internal account balance. You can do these checks with public addresses and transaction IDs, without connecting a wallet or signing anything.

What does each balance count?

Bitcoin records outputs that later transactions can spend. An unspent transaction output (UTXO) is one such piece of BTC, rather than a running account entry. The Bitcoin transaction guide explains how a wallet balance comes from these outputs.

Number on the screen	What to establish	What it does not prove
Confirmed address balance	Which address and confirmed chain state it uses	That no pending transaction already spends its outputs
Pending or unconfirmed amount	Incoming, outgoing or net change seen by that service	That a payment is settled or will confirm by a deadline
Available or spendable wallet balance	The wallet’s addresses, pending activity and spending rules	That it equals one address’s confirmed balance

Labels vary. In Bitcoin Core’s balance categories, trusted funds can include outputs created by the wallet, while pending outputs from others have a separate category. So “trusted” and “confirmed” are not interchangeable labels. Your own wallet’s current documentation determines what its available figure means.

A pending receipt can be missing from a confirmed total

For an invented example, an address has 100,000 satoshis confirmed. A new transaction pays it 50,000 sats, but has not entered a block. One BTC is 100,000,000 sats.

The confirmed-only amount remains 100,000 sats (0.001 BTC). A view including that pending receipt might show 150,000 sats (0.0015 BTC). The extra 50,000 is still pending, not a second confirmed holding.

Open the transaction from your receiving wallet or search its full transaction ID in Blockstream Explorer. Check that an output pays the exact receiving address and amount, and read the confirmation state. Blockstream’s lookup guide explains these fields. Seeing a transaction in a mempool means that service knows an unconfirmed transaction; it does not guarantee inclusion or a fixed waiting time.

A public explorer receives the address or transaction ID you look up. Use your own explorer if that privacy boundary matters. A seed phrase, private key or extended public key is unnecessary for this check.

A pending send can leave the old confirmed balance visible

Now take a different fictional case. Address A holds only one confirmed 100,000-sat output. Your wallet spends that output and creates two outputs:

• 30,000 sats for the recipient;
• 69,000 sats of change at a new address B in your wallet.

The 1,000-sat fee is the difference between the input and those two outputs. These are arithmetic assumptions, not a fee recommendation or a real transaction. The total is 30,000 + 69,000 + 1,000 = 100,000 sats.

While this transaction is unconfirmed, a chain-only view of A can still show 100,000 sats. Your sending wallet can already reserve that input and recognize the pending change. It does not follow that you have 100,000 freely available at A plus another 69,000 at B.

After confirmation, in this isolated example with no other activity, A has zero and B has 69,000 sats (0.00069 BTC). A tracker watching only A will miss the change at B. Nothing in that observation alone establishes a loss of the wallet’s remaining BTC.

The Bitcoin guide’s change explanation describes why wallets return surplus value to a change output, often at a new address. Identify B from your own wallet’s transaction details. Output order or an explorer’s guess is not proof that an address belongs to you. Do not change your wallet’s address-reuse practices just to make a tracker easier to read.

Why can an unconfirmed amount be negative?

Some address views show the net effect of pending transactions. If they spend more from that address than they pay to it, the pending difference is negative. This is an adjustment to address accounting, not a Bitcoin debt.

The Esplora API exposes separate chain_stats and mempool_stats counters for outputs funded and spent. For a confirmed-only address figure, subtract confirmed spent_txo_sum from confirmed funded_txo_sum. The analogous mempool difference may be below zero because it can spend previously confirmed outputs.

A service may combine these figures, display them separately or apply a wallet-specific policy. Do not add a pending amount again when a displayed total already includes it. An address calculation also does not determine which outputs your wallet will let you spend: Bitcoin Core’s output reference distinguishes output safety and wallet selection conditions.

Reconcile the figures without moving BTC

1. Fix the comparison. Record Bitcoin Mainnet, the full address or address set, the time, the BTC or satoshi amount and each screen’s label. Compare quantities before dollar estimates. An exchange account or Lightning balance needs a different record.
2. Find the exact transaction. Use the transaction ID from your wallet. Confirm the receiving outputs and any inputs it spends. Read whether the transaction is unconfirmed or included in a block. Keep the wallet’s current replacement/conflict information if it shows any; a missing result on one explorer is not proof of cancellation.
3. Account for your change. Use your wallet to identify the output returned to you. Compare a tracker for A with A, or a whole-wallet view with the same owned address set. Never count the old input and the outputs created by the pending transaction as independent holdings.
4. Refresh both views and verify the result. After the relevant confirmation and a successful data refresh, compare the matching outputs and address scope again. If the difference remains, keep the transaction ID, scope and timestamps for the wallet’s official support route. Do not resend a payment merely to repair a display discrepancy.

A first confirmation means inclusion in a block; later blocks increase its confirmation depth. The receiving service sets its own acceptance rules. There is no universal confirmation count or guaranteed elapsed time that makes every screen call funds available.

If your other mismatch concerns missing prices or a failed network response, the portfolio balance checklist covers those separate checks. For several tracked addresses, see the multiple-wallet guide.

What does Owlio’s Bitcoin amount show?

For the publicly listed Owlio 1.1.0, checked on 4 November 2026, the Bitcoin adapter calculates an added address’s amount from confirmed chain counters only. It does not include the mempool adjustment. An incoming payment can therefore be absent until confirmation, while an unconfirmed outgoing spend can leave an older confirmed figure visible.

Treat that as an address-tracking boundary. Owlio does not establish which pending outputs your sending wallet considers safe, and one added address does not discover every receiving or change address in your wallet. Check the relevant data status and compare the same public address with an explorer; use your sending wallet for its own available balance and ownership of change.

Your completed check should leave you with a labelled confirmed address amount, a separate account of pending activity, and your wallet’s available figure for the intended address set. Keep them as different observations until their states and scopes match.