A confirmation is a transaction being included in a block; more confirmations mean deeper burial under later blocks, making reversal practically impossible. This bytrade Education Center guide explains the counts that matter.
One confirmation means the network accepted the block; six is the traditional threshold for high-value Bitcoin transfers because rewriting six blocks is economically absurd. Different chains finalize differently — some reach mathematical finality in seconds, others only accumulate probability.
For exchanges, the required confirmation count is set by the receiving platform, not by you. For personal transfers between wallets you control, one confirmation on a healthy chain is generally fine; for large amounts, waiting for a handful more costs minutes and buys certainty.
The confusing case is a "stuck" transaction: sent with too low a fee, it can sit unconfirmed for hours. It is not lost — it is unaccepted. Resending the same amount with a different fee before the original is mined can accidentally double-spend yourself; use the explorer to check status first.
A practical example: a Bitcoin transfer broadcast on a Saturday night during a fee spike can sit for hours with one confirmation pending. The explorer shows the fee paid versus the current mempool median — the transaction is visible, healthy and simply waiting its turn.
The explorer also answers whether a resend is safe: if the original transaction is still in the mempool, broadcasting a second identical transfer with a higher fee replaces it only if the wallet supports replace-by-fee — otherwise the resend can confirm twice.
- How long is too long to wait?
- Check the transaction hash on an explorer: pending means queued; failed means rejected. Hours of pending usually means a fee below network conditions.
- Why do networks need confirmations at all?
- Reorganization is rare but possible near the chain tip. Buried blocks make rewritten history progressively uneconomical.