How Long Does a Bitcoin Transaction Take? Confirmations, Fees and Fixes

A Bitcoin transaction is broadcast to the network within seconds, but a transfer is only “confirmed” once a miner includes it in a block, and Bitcoin blocks are found roughly every 10 minutes on average. As of 27 October 2026, the mempool is nearly empty: mempool.space’s fee API returns 1 sat/vB across every tier, so a transfer paying even the minimum fee should confirm in the next block. Exchanges still wait for two to three confirmations before crediting a deposit, which is why a Bitcoin deposit into Binance, Coinbase or Kraken typically takes about 20 to 45 minutes rather than 10.

How long does a Bitcoin transaction take to confirm?

A transaction gets its first confirmation when a miner places it in a block, and the Bitcoin network targets one block roughly every 10 minutes, though this is an average with no guaranteed maximum. Most wallets show funds as received after one confirmation, but the long-standing safety standard is six confirmations, around an hour, before a payment is treated as settled.

Bitcoin’s block interval is not a clock. Bitcoin.org describes block discovery as probabilistic: the average is about 10 minutes, but there is no guaranteed minimum or maximum, and a single block can take 30 minutes or more. Each block after the one that contains your transaction adds one more confirmation, so a six-confirmation settlement normally lands close to an hour later. For more on how mining and blocks set that rhythm, see our Bitcoin explainer.

One confirmation is enough for most small payments because it already makes a double-spend expensive to attempt. Six confirmations is the convention for larger amounts and for finality, matching Bitcoin.org’s description of six confirmations as safe as a settled card payment. The exact number is your choice: a merchant or an exchange sets its own threshold, and the next sections cover the exchange side.

Why is my Bitcoin transaction taking so long to confirm?

Miners pack each block with the transactions that pay the highest fee per byte, so when the network is busy a low-fee transfer can wait several blocks or hours. As of 27 October 2026 the mempool is nearly empty and mempool.space lists 1 sat/vB across every recommended tier, so delays are currently short, but the same transfer can sit for hours whenever demand for block space rises.

The fee you pay is not based on the amount sent; it is based on the transaction’s size in bytes, as Bitcoin.org explains. A transaction that spends several smaller inputs, or a multisig transaction, is larger and costs more. As an illustrative example, a simple SegWit transfer of roughly 140 vbytes costs about 140 satoshis at 1 sat/vB, about 1,400 satoshis at 10 sat/vB and about 7,000 satoshis at 50 sat/vB. Higher fee rates move a transfer to the front of the queue, and most wallets suggest a fee automatically while letting you review it before sending.

Unconfirmed transactions wait in a mempool, and there is no single global mempool: each node keeps its own view of valid but unconfirmed transactions, per the Bitcoin Wiki. When blocks are full, low-fee transfers sit at the back; when demand clears, even cheap transfers confirm. A node also drops an unconfirmed transaction after a default expiry of 336 hours (14 days), a limit set in Bitcoin Core’s source code, after which the funds return to your wallet.

How many confirmations do exchanges require before crediting Bitcoin?

Exchanges do not credit Bitcoin at the first confirmation. Binance and Coinbase each require 2 confirmations, and Kraken requires 3, which its help centre estimates at about 45 minutes using a 15-minute block assumption; Coinbase’s help centre now lists 2 confirmations for Bitcoin. KuCoin says the requirement varies by coin and network and is shown on its deposit page.

These figures come from each exchange’s help centre. Binance states a Bitcoin transaction needs “at least 2 network confirmations” before the deposit is credited. Coinbase’s confirmations glossary lists Bitcoin at 2 confirmations, and its Exchange help page shows network_confirmations of 2. Kraken credits Bitcoin after three confirmations, about 45 minutes. KuCoin notes confirmations vary by coin and that crediting can take up to 2 to 3 hours after the threshold is met. Withdrawals follow the same block timing in reverse, once the exchange broadcasts the transaction on-chain. Our exchange hub and the reviews of Binance, Coinbase, Kraken and KuCoin cover fees and safety in more detail.

Can a Bitcoin transaction get stuck? How do you fix it?

A transfer that pays too little can remain unconfirmed, and Bitcoin Core nodes drop an unconfirmed transaction after a default 336 hours (14 days). Two techniques can push it through: replace-by-fee (RBF), which swaps the pending transaction for one paying a higher fee, and child-pays-for-parent (CPFP), where a second transaction spending the pending output overpays so a miner includes both.

Replace-by-fee follows the rules in BIP-125. A replacement must spend at least one of the same inputs and pay a higher total fee, and the original transaction has to signal that it is replaceable. Many wallets, including Electrum, offer a “bump fee” action that does this for you.

Child-pays-for-parent works from the receiving side. As the Bitcoin Wiki explains, you create a child transaction that spends an output of the stuck parent and pays a much higher fee rate, which encourages a miner to include both in the same block. Not every wallet exposes CPFP, so check whether yours does before relying on it. Never share your seed phrase with anyone offering to “unstick” a transaction; that is a common phishing scam, and neither RBF nor CPFP ever requires it.

Is there a faster way to send Bitcoin?

Yes. The Lightning Network settles payments off-chain between participants and describes payment speed as measured in milliseconds to seconds, removing the block confirmation wait for small transfers. It still uses real Bitcoin transactions to open and close channels, so it is a speed layer on top of Bitcoin rather than a separate coin.

Lightning moves frequent, small payments off the blockchain and settles them between channel participants, so there is no 10-minute wait per payment and fees are exceptionally low. Opening and closing a channel are on-chain Bitcoin transactions, and closing broadcasts the latest balance to the blockchain, so the base layer still settles the final state. Lightning suits small, time-sensitive payments; large or infrequent transfers are fine on-chain. See our wallet guides for software and hardware wallets that support both routes.

A dated timeline of Bitcoin confirmation time

Bitcoin’s roughly 10-minute block target and the practice of waiting for several confirmations have stayed stable since launch, but fee levels and exchange requirements have shifted over time. These dated milestones show when the key rules were set and how they stand today.

What should users do now?

Before sending, check the mempool and set a fee at or above the current minimum; as of 27 October 2026, 1 sat/vB is enough, but a higher fee confirms faster when demand returns. If a transfer is pending, confirm it on a block explorer, then use RBF or CPFP if your wallet supports them, and check the exchange’s required confirmations before assuming a deposit is lost.

• Look up your transaction ID on a block explorer to see how many confirmations it has and its fee rate.
• Compare the fee rate to the current recommendations on mempool.space before sending.
• If a transfer is stuck, use the “bump fee” (RBF) option or a CPFP child transaction if your wallet offers them.
• Verify the destination address and network before re-sending, and never share your seed phrase with anyone offering to speed up a transaction.
• For a deposit, wait for the exchange’s required confirmations: 2 for Binance and Coinbase, 3 for Kraken.
• Once a deposit is credited, consider moving long-term holdings to a wallet you control, following our withdrawal guide.

Crypto assets are volatile and this is not financial advice. Transaction timing depends on network conditions, so the figures here are averages and estimates, not guarantees.