By Why Do Bitcoin Transactions Take So Long Sometimes?
You send a payment and it confirms in ten minutes. Next week you send a similar one and it's still sitting there three hours later. Nothing about your transaction necessarily changed. What changed is everyone else's transactions competing for the same limited space.
It's an auction, and you're not the only bidder
Every unconfirmed transaction sits in the mempool waiting for a miner to include it in a block, and blocks only come along roughly every 10 minutes with a fixed amount of room in each one. Miners generally pick whichever transactions pay the most per byte first, so when a lot of people are all trying to transact at once, low-fee transactions simply get pushed further back in the queue. We cover the fee side of this in more depth in what a Bitcoin transaction fee actually is, but the short version is: your wait time is really a function of how much you bid relative to everyone else bidding at that exact moment.
Network congestion isn't constant
Demand for block space rises and falls, sometimes predictably (some days of the week tend to run busier than others) and sometimes not (a sudden spike in activity across the network can back the mempool up fast). A fee that would've gotten you confirmed within one block last Tuesday might leave you waiting for several blocks today, through no fault of your own.
What actually helps if you're stuck
- Replace-By-Fee (RBF): if your wallet supports it and you flagged the transaction as replaceable when sending, you can rebroadcast it with a higher fee to jump the queue.
- Child-Pays-for-Parent (CPFP): if you're the one waiting to receive funds, you can sometimes attach a new, high-fee transaction spending the unconfirmed output, which effectively bribes miners to confirm both together.
- Just wait it out: an unconfirmed transaction with a reasonable fee will generally confirm eventually as the backlog clears, it just might take longer than you'd like.
One thing worth knowing: a transaction sitting unconfirmed hasn't failed. It's valid and waiting, not stuck in some broken state, unless it eventually gets dropped from nodes' mempools for sitting too long with too low a fee, which does happen for very underpriced transactions after enough time passes.
Why this isn't really a flaw
A fixed block size and roughly 10-minute block time are deliberate design choices, not accidental limitations, and they're part of what keeps a full node's storage and bandwidth requirements from spiraling out of control, which in turn is part of what keeps the network decentralized rather than only runnable by big, well-resourced operators. Layer-2 systems like the Lightning Network exist specifically to route most everyday payments around this bottleneck entirely.
Every Bitcoin private key that will ever exist is generated right here on this site, Satoshi's included. Try for a million years. You still won't find a funded one.
Try the key collider nowBottom line
A slow confirmation almost always comes down to fee versus current demand, not anything wrong with your transaction. For the full path a transaction takes from your wallet to the blockchain, see what happens when you send Bitcoin.