Bitcoin Send Max can leave a balance when it applies only to the selected account or outputs, when coins are excluded from spending, or when small outputs are uneconomic at the chosen fee rate. Identify the remaining UTXOs before calling them dust. The fee paid by a completed transaction is not the same thing as an unspent remainder still shown in your wallet.
Locate the remainder before trying to remove it
Check which account the completed send used and which account the remaining balance belongs to. A wallet application can summarize several accounts while its send form operates on one. Next inspect the transaction's inputs and outputs, and the wallet's current unspent-output list. An old address can have received more than one output, so an address alone may not identify the specific remainder. Record its creating transaction and output index.
A UTXO is an individual spendable output, not a decimal fragment in a single account balance. Your investigation should answer whether the remainder was left untouched, returned as change, received later or merely appears in a stale display. Those possibilities require different evidence. Do not send another transaction just to make the main screen reach zero before you understand what it represents.
Use the output's status to choose the next check
| Remaining record | Likely question | Evidence to inspect | Avoid this assumption |
|---|---|---|---|
| Balance in another account | Was the send scoped to one account? | Account name and selected source | Max meant every account in the app |
| Output outside a manual selection | Was only the selected set spent? | Actual transaction inputs versus selection | The wallet forgot part of the payment |
| Locally locked output | Was it excluded deliberately? | Wallet lock state and notes | A blockchain fee will unlock it |
| Unconfirmed incoming output | Does the wallet currently allow it? | Creating transaction and wallet policy | Every displayed satoshi is immediately selectable |
| Small recognized output | Does spending it add more fee than value? | Current construction estimate | A small face value is automatically economical |
| Change from a fixed-amount send | Was Max actually enabled? | Recipient amount and change output | Every send form with a Max button used that option |
There is a product-specific example in BitBoxApp's coin-control instructions: Send all uses the current account's available value minus the fee, while Send selected coins uses the selected outputs. A fixed-amount payment can leave unused outputs or create change. Check your own wallet's wording rather than treating all buttons named Max as identical.
Reconcile the numbers without inventing a fee reserve
Consider a fictional account with outputs of 100,000 sats and 30,000 sats. You select only the first output, and a maximum-from-selection transaction spends it with a 1,000-sat fee. The recipient gets 99,000 sats and the 30,000-sat output stays unspent. The wallet has not withheld 30,000 sats as a fee. It used the permitted source and left the other output untouched.
Now consider a fixed payment using that 100,000-sat input: 90,000 sats go to the recipient, 1,000 sats are the fee, and 9,000 sats return as change. That is a different construction, despite starting from the same input. Inspect the actual transaction instead of inferring which mode was used from memory. Our input-count fee explanation shows why the chosen sources matter to cost.
Both examples are arithmetic illustrations, not current fee estimates or suggested transaction sizes. In a Bitcoin transaction, inputs already consumed by that transaction cannot simultaneously remain as those same unspent outputs. If an apparent remainder shares an old address, inspect the outpoint carefully: it may be a different output or newly created change. This distinction is more useful than a rounded fiat total.
Separate a wallet lock from an economic exclusion
Bitcoin Core documents locally locked outputs separately from ordinary spending availability. A deliberate lock can preserve an output for your own organizational or privacy reasons. Read the reason before changing it. A stranger asking for an unlocking payment does not establish that a network-level lock exists or that the payment will affect your wallet's local selection.
Core's versioned sendall documentation also distinguishes eligible inputs and an option that excludes outputs unable to pay their own spending cost. That is a specific implementation, not proof that your wallet chose the same policy. A coin can exist and remain controlled by your keys while its inclusion would reduce the net amount received at a particular fee rate.
Dust is not one universal balance threshold
Dust relay policy concerns output construction and policy assumptions. Bitcoin Core's policy implementation considers the output and estimated spending characteristics with the configured dust relay fee. Do not apply a single number to every script type and call every smaller displayed balance unspendable forever. Policy dust and the economic decision to include an existing input are related but different questions.
For an unfamiliar tiny incoming output, identifying its origin matters before combining it with your other coins. Clearing a small display balance is not automatically worth the fee or the information revealed by linking sources. Preserve intentional exclusions while investigating. You can read the output list and review a draft construction without broadcasting a consolidation transaction.
- Record the wallet account and the exact remaining output, including its transaction identifier and index.
- Compare that output with the inputs actually spent by the completed payment.
- Check manual selection, local locks and confirmation restrictions in the wallet's documentation.
- Distinguish untouched outputs from change and later receipts.
- Review spending cost and source relationships before deciding whether to include the remainder in any future send.
- Verify recipient amount and fee independently; retain a correct payment receipt even if another output remains.
An exact-amount order may be incompatible with your cleanup goal
For a no-account swap, follow the current order's amount and receiving instructions. Maximizing the wallet payout is a different goal from paying a specified amount. Do not deliberately overpay an order merely to remove a leftover or assume an extra tiny transaction will be combined automatically. If the first payment's broadcast result is uncertain, inspect its history before doing anything else. A nonzero remaining wallet balance does not, by itself, indicate that the recipient was underpaid.
FAQ
What does Bitcoin Max Send mean?
It usually calculates a payout from the available source after the transaction fee, but its scope depends on the wallet. Verify whether it covers the current account or only selected coins.
Can frozen coins explain a remaining Electrum balance?
A wallet-local exclusion can prevent an output from being selected while leaving it visible. Check the specific wallet's lock or freeze state and its purpose before changing it.
Is there one Bitcoin dust threshold for every remainder?
No universal displayed-balance threshold answers every case. Output policy, script characteristics and the current cost of spending an existing input must be distinguished.