Bitcoin Confirmation Time Calculator by Fee Rate

How Bitcoin Confirmation Time Works

Bitcoin confirmation time is the delay between broadcasting a transaction and having it included in a mined block. This delay is not fixed: it depends on the fee rate you attach to the transaction, the current state of the mempool, and the inherently random interval between blocks. A transaction paying 100 sat/vB during a quiet mempool might confirm in under two minutes. The same fee rate during a congestion spike could leave you waiting for hours.

Miners select transactions from the mempool in descending order of fee rate (satoshis per virtual byte) to maximize revenue. Your transaction's position in this queue determines when it gets included. The table below maps fee rate ranges to expected confirmation times under three congestion scenarios.

Fee Rate vs. Confirmation Time by Congestion Level

Congestion levels are based on total mempool size in virtual megabytes (vMB). Low congestion corresponds to a mempool under 30 vMB, medium to 30-100 vMB, and high to over 100 vMB. When the mempool drops below roughly 1 vMB, even the minimum relay fee confirms in the next block.

These are estimates, not guarantees. Block production follows a Poisson process, meaning "next block" could arrive in 30 seconds or 40 minutes. The fee rate ranges above shift during extreme events: the April 2024 Runes launch pushed next-block fees above 1,000 sat/vB, while quiet periods in mid-2025 saw entire blocks filled at 1 sat/vB. For real-time fee data, use our Bitcoin fee estimator.

Why Block Times Are Unpredictable

Bitcoin targets a 10-minute average block interval, but the actual distribution is exponential, not uniform. Analysis of over 670,000 blocks shows the observed mean is approximately 9 minutes 38 seconds, while the median is just 6 minutes 52 seconds. The gap between mean and median reflects the distribution's long tail: most blocks arrive quickly, but some take much longer.

The mathematical explanation: Bitcoin mining is a memoryless process. The probability of finding the next block in any given second is constant regardless of how long miners have already been searching. The inter-block time follows an exponential distribution with parameter λ = 1/600. The theoretical cumulative probability at 10 minutes is 1 - 1/e ≈ 63.2%, closely matching the observed 63%.

For users waiting on a specific number of confirmations, the variance compounds. Six confirmations (the standard for large transactions) take under 60 minutes only about 57% of the time, under 80 minutes 81% of the time, and under 2 hours roughly 98% of the time.

How Many Confirmations Do You Need?

The number of confirmations required depends on the value being transferred and the acceptable level of double-spend risk. Each additional confirmation makes reversal exponentially harder. Satoshi's whitepaper quantified this: against an attacker with 10% of the network hashrate, one confirmation leaves a 5.1% chance of successful reversal, while six confirmations reduce it to 0.006%.

These probabilities assume the attacker is racing with raw hashrate. In practice, exchanges like Coinbase require 2 confirmations for BTC deposits, balancing security against user experience. For a deeper analysis, see our research on Bitcoin transaction lifecycle.

Fee Estimation Methods

Two fundamentally different approaches exist for estimating the right fee to achieve a target confirmation time.

Confirmation-based estimation (Bitcoin Core): tracks historical confirmation rates across fee rate buckets using an exponentially decaying moving average. Bitcoin Core evaluates three time horizons: a short window with an 18-block half-life, a medium window at 144 blocks, and a long window at 1,008 blocks. The conservative mode requires the 95th percentile success threshold at double the target across all horizons. The economical mode uses only the shortest applicable horizon, making it more responsive to fee drops. As of Bitcoin Core v28, economical mode is the default, reflecting the availability of Replace-By-Fee as a safety net.

Mempool-based estimation (mempool.space): inspects every unconfirmed transaction in the current mempool, projects which transactions would fill the next several blocks, and determines the minimum fee rate needed for each confirmation target. This approach reacts instantly to mempool changes but can be manipulated by flooding the mempool with high-fee transactions that are never mined.

Neither method is perfect. Confirmation-based estimation is slow to react to sudden congestion spikes. Mempool-based estimation can't predict transactions that haven't been broadcast yet. The most reliable strategy: use mempool-based estimates for next-block targets and confirmation-based estimates for longer horizons.

Using RBF to Unstick a Transaction

If your transaction is stuck in the mempool because the fee rate was too low, Replace-By-Fee (RBF) lets you broadcast a replacement with a higher fee. Since Bitcoin Core v28 (2024), full RBF is enabled by default across the network: any unconfirmed transaction can be replaced regardless of whether it originally signaled RBF opt-in via nSequence.

The replacement must satisfy two fee rules: first, the absolute fee must be at least equal to the sum of all original transactions' fees. Second, an additional fee covering the replacement's own bandwidth at the incremental relay fee rate (currently 0.1 sat/vB as of Bitcoin Core v29.1) must be included. For example, a 500 vB replacement needs at least 50 additional satoshis above the original fee total.

Most modern wallets support RBF natively. Bitcoin Core's bumpfee RPC command handles the replacement automatically. Hardware wallets and mobile wallets typically offer a "speed up transaction" button that constructs the replacement behind the scenes. For a detailed comparison of fee bumping methods, see our RBF vs CPFP comparison and the research article on fee bumping strategies.

Tip: Always enable RBF when sending transactions. If you overpay, you can't reduce the fee after broadcast. But if you underpay, RBF gives you a path to confirm without waiting for the mempool to clear.

Historical Congestion Events

Understanding past congestion spikes helps calibrate expectations. The fee market has experienced several dramatic events that pushed confirmation times from minutes to days for low-fee transactions.

The contrast is stark: during the April 2024 Runes launch, users paid over 2,600% more than typical fees. Six months later, the mempool was frequently empty. This volatility is inherent to Bitcoin's block space market. For ongoing mempool monitoring, see our fee rate history tool.

Bypassing Confirmation Delays Entirely

On-chain confirmation delays are a fundamental constraint of Bitcoin's base layer. Several protocols eliminate the wait by moving transactions off-chain while retaining Bitcoin's security guarantees.

The Lightning Network routes payments through pre-funded payment channels, settling in milliseconds rather than minutes. Lightning is ideal for small to medium payments but requires channel management and sufficient inbound liquidity.

Spark takes a different approach as a Bitcoin Layer 2 that supports instant transfers of both bitcoin and stablecoins like USDB without requiring users to manage channels or worry about liquidity. Transactions on Spark settle in seconds with near-zero fees, making confirmation time a non-issue for everyday payments. For a deeper comparison, see our research on Lightning vs Spark and the Spark protocol overview.

Frequently Asked Questions

How long does a Bitcoin transaction take to confirm?

A Bitcoin transaction typically confirms in 10 to 60 minutes, depending on the fee rate and mempool congestion. With a sufficiently high fee rate (top of the mempool), the median wait for the next block is about 7 minutes. With a low fee rate during congestion, a transaction can remain unconfirmed for hours or days. The "10-minute average" is a statistical property of block production, not a promise for any individual transaction.

What happens if my Bitcoin transaction is unconfirmed for days?

An unconfirmed transaction remains in the mempool until a miner includes it in a block or nodes drop it from their mempools (typically after 14 days by default in Bitcoin Core). During this time, you can use RBF to replace it with a higher-fee version, or a recipient can use CPFP to incentivize miners to confirm it. If the transaction is eventually dropped, the funds return to the sender's wallet.

How do I speed up a stuck Bitcoin transaction?

The two standard methods are RBF and CPFP. With RBF, the sender broadcasts a replacement transaction spending the same inputs but with a higher fee. With CPFP, the recipient creates a new transaction spending the unconfirmed output with a high enough fee to make the package attractive to miners. Most wallets now support RBF natively through a "speed up" or "bump fee" option.

Why is my Bitcoin transaction taking so long even with a high fee?

Block intervals are random, not fixed. Even if your transaction has the highest fee rate in the mempool, the next block could take 30 or even 60 minutes to arrive: roughly 5% of blocks take over 30 minutes, and 1-2% take over an hour. Additionally, during sudden congestion spikes (like the April 2024 Runes launch), what seemed like a "high" fee may have been undercut by a flood of even higher-fee transactions.

How many sat/vB do I need for next-block confirmation?

It depends entirely on current mempool conditions. During low congestion (mempool under 1 vMB), even 1 sat/vB confirms in the next block. During medium congestion, 20-50 sat/vB is usually sufficient. During high congestion events, next-block rates can exceed 500 sat/vB. Check real-time estimates at our fee estimator before sending.

Can I cancel an unconfirmed Bitcoin transaction?

Bitcoin has no native cancel mechanism, but you can effectively cancel a transaction using RBF by sending a replacement that pays the funds back to your own address with a higher fee. This works because the replacement spends the same inputs, invalidating the original transaction. Since Bitcoin Core v28, full RBF is the network default, so any unconfirmed transaction can be replaced.

What is the difference between 1 confirmation and 6 confirmations?

One confirmation means your transaction is included in a single mined block. Six confirmations mean five additional blocks have been built on top of it, making reversal extremely expensive. The six-confirmation standard originates from Satoshi's whitepaper analysis: against an attacker controlling 10% of the network hashrate, the probability of reversing a transaction drops from 5.1% at one confirmation to 0.006% at six. Most exchanges require 2-3 confirmations for deposits, while high-value settlements typically wait for 6.

This tool is for informational purposes only and does not constitute financial advice. Confirmation time estimates are approximate and based on historical data and publicly available mempool research. Actual confirmation times depend on real-time network conditions. Fee rate ranges shift with demand: always check current mempool state before setting transaction fees.