A Bitcoin send has three moving parts that deserve separate attention: the amount reaching the recipient, the fee paid for the transaction, and the confirmations that follow. A wallet may display all three in one activity entry, but each answers a different question. Understanding them helps explain why a send can appear in an explorer before an exchange credits it, or why a transaction includes an unfamiliar change address.
This guide covers ordinary transactions on the Bitcoin blockchain. Begin with the Bitcoin send overview if you need to distinguish the network from other transfer routes. The aim is to read a proposed transaction accurately and follow its progress with evidence.
First establish which Bitcoin route the recipient accepts
The asset label BTC is only the beginning of the check. Ask for the recipient's current deposit or receiving instructions and establish that both sides support an onchain Bitcoin transfer. A service may display other routes beside Bitcoin. A Bitcoin withdrawal, a Lightning payment, and a token representing bitcoin on another blockchain have different requirements. A familiar asset name does not make those destinations interchangeable.
Read the destination instructions before copying an address. If a receiving service specifies a network, minimum deposit, or confirmation requirement, keep that information with the transfer record. Do not choose a cheaper network from a withdrawal menu unless the receiving service explicitly supports that exact route for the asset. When instructions are unclear, resolve the mismatch before preparing the send.
Why a wallet balance can involve several inputs
Bitcoin records spendable amounts as unspent transaction outputs, usually shortened to UTXOs. A wallet balance can be the sum of several such outputs. When the wallet builds a payment, it selects outputs to spend and uses them as transaction inputs. The transaction then creates new outputs for the intended recipient and, where needed, the sender's remaining funds.
Selected outputs are spent in full. Any difference between their combined value and the new output values becomes the transaction fee. The Bitcoin developer guide to transactions explains this relationship between inputs, outputs, fees, and change. It is useful background when an explorer's transaction total looks larger than the amount you intended to send.
A simple change example
Imagine a wallet selecting an input worth 100,000 satoshis for a payment of 60,000 satoshis. Suppose the proposed fee in this illustrative example is 2,000 satoshis. The remaining 38,000 satoshis can return to the wallet through a change output. Those figures describe the arithmetic only; they are not a suggested fee or a current network quote.
The recipient amount is 60,000 satoshis, even though the transaction spends a larger input. Before signing, use the wallet's transaction review to identify the recipient, fee, and change. If a hardware wallet displays change information, review it there as well. An explorer may show addresses without knowing which belongs to you, so unfamiliar presentation alone is not evidence that money went missing.
How to read a Bitcoin fee estimate
A Bitcoin network fee depends on the space the transaction requires and the fee rate attached to it. Wallets commonly express that rate in satoshis per virtual byte, written sat/vB. Virtual size is a transaction measurement used for fee calculation. A payment using many inputs can require more space than one using fewer inputs, even when its recipient amount is smaller.
For an illustrative calculation, a transaction estimated at 150 virtual bytes with a proposed rate of 10 sat/vB would have an estimated fee of 1,500 satoshis. This is an arithmetic example, not a live recommendation. Review the wallet's current estimate and the final total before signing, because transaction construction and network conditions affect the proposal.
Keep a service's withdrawal charge separate from the blockchain fee. If an exchange presents a charge, use its own breakdown to establish what you will pay and what the recipient should receive. A transaction visible onchain may contain several outputs, so its total network fee does not automatically identify the charge assigned to your individual withdrawal.
Choose a target that matches the transfer
A faster fee option expresses a desired confirmation target; it cannot reserve a particular block. Think about the actual deadline. A transfer to another wallet you control may have different timing needs from a deposit needed for a time-sensitive action. Leave room for the receiver's processing requirement as well as blockchain confirmation.
A very low fee can mean a longer wait, while a higher fee can increase cost without resolving an address or network problem. Compare the proposed fee with the amount being sent. If the fee makes the transfer impractical, consider postponing the transfer. The guide to lower crypto transfer fees explains how to evaluate cost without sacrificing compatibility.
Broadcasting, confirmation and crediting are different stages
Broadcasting makes a signed transaction available to the network. It does not itself establish that the transaction has entered the blockchain. An unconfirmed transaction has no block confirmation. Its first confirmation comes when it is included in a block; additional blocks extending that chain increase its confirmation count.
Block discovery is variable, so confirmation timing is not a countdown. Fee competition can also affect when inclusion occurs. A sender should avoid interpreting an estimated arrival time as a promise. A recipient should follow a confirmation policy appropriate to the transfer and, for a hosted account, the service's stated deposit rules.
Exchange crediting is another check. A transaction can have confirmations while the account still awaits the exchange's required threshold or processing. Compare the blockchain record with the deposit instructions before deciding there is a fault. Record the transaction ID so any later support request identifies the actual transfer rather than just a balance change.
Review the complete send before signing
Use the same review order each time. Start with the network and asset, then compare the complete recipient address with the trusted receiving instructions. Check the recipient amount, the fee, and the total debit. If the wallet offers a subtract-fee option, establish whether it changes the amount delivered to the recipient. The wording and defaults can differ between applications.
For a new destination, a small test can help check the route, provided it meets any deposit minimum and the cost is acceptable. Confirm its actual arrival before relying on it. A successful test does not remove the need to review the later transfer. The wallet send checklist provides a consistent review sequence across supported wallets.
What to do with a pending Bitcoin transaction
Find the transaction ID in the sending wallet or service and inspect it on the correct Bitcoin network. Compare its outputs, amount, and confirmation status with your record. If a hosted service has not supplied a transaction ID, check its withdrawal status first. There may not yet be a broadcast transaction to diagnose.
Some wallets can replace an unconfirmed transaction with one paying a higher fee. Availability depends on the wallet and transaction conditions. Use the wallet's documented fee adjustment workflow, review the new cost, and retain any replacement transaction ID. Do not create another independent payment just because the original remains pending; both could eventually reach the recipient.
If the status remains unclear, follow the pending crypto transfer troubleshooting guide to separate a broadcast problem, blockchain delay, and receiving-service delay. Avoid sharing recovery phrases or private keys with anyone offering help.
Keep a transfer record that can be checked
Save the transaction ID with the recipient amount, selected network, and the receiving instructions used for the transfer. If the wallet replaces the transaction, keep the new ID alongside the original one. This makes it easier to explain why a pending entry changed without losing track of the intended payment.
When comparing balances, use the recipient output and the wallet's final fee record. A currency-converted balance can move for reasons unrelated to the transfer amount. Reconcile the bitcoin amounts first, then check any displayed currency conversion separately.
Conclusion: reconcile the amount, fee and final status
A well-reviewed Bitcoin send has a clear recipient output, an understood fee, and a destination that supports the selected route. Change explains why the transaction can involve more bitcoin than the payment amount. Confirmations explain its progress onchain, while the recipient's own record establishes whether a hosted deposit has been credited. Keep those details together until the transfer is reconciled.
