You sent crypto and it's been sitting there, pending, for way longer than you expected. Before you panic, here's what's actually happening and what you can do about it.
How Crypto Transactions Actually Work
Unlike a bank transfer, a crypto transaction doesn't get processed instantly by a central server. When you hit send, your transaction goes into a waiting area called the mempool — a queue of pending transactions waiting to be included in the next block. Miners or validators pick transactions from this pool, usually prioritizing the ones with the highest fees. If your fee is too low relative to current demand, your transaction waits.
Cause 1: Your Fee Was Too Low
This is the most common reason. When network activity spikes, the cost of getting into the next block goes up. If you set a low fee — or your wallet auto-set one during a quiet period that then got busy — your transaction gets stuck behind higher-paying ones. On Bitcoin, you can check the current fee environment using a mempool explorer. On Ethereum, gas trackers show the current gwei price. Our gas fees guide covers how to read these.
Fix: Wait — fees fluctuate throughout the day, and yours may clear when traffic drops. If you need it confirmed faster, most wallets support a "replace by fee" (RBF) feature that lets you resubmit the same transaction with a higher fee.
Cause 2: The Network Is Congested
Sometimes it's not your fee — it's the network. During high-traffic events (a popular NFT mint, a market crash triggering a wave of liquidations, a major exchange issue), even appropriately-priced transactions can take longer. Bitcoin and Ethereum can only process so many transactions per block. When demand exceeds capacity, everything slows down.
Fix: Patience. Check a block explorer to see if the network is genuinely congested. If it is, your transaction will confirm when the backlog clears — usually within hours, not days.
Cause 3: You Sent to the Wrong Network
This is the scary one. If you sent Ethereum (ETH) on the Ethereum network to an address that's on a different network — like sending to a BNB Chain address without using the right bridge — the transaction may show as "completed" on the blockchain but never arrive at the destination. It's not pending in the traditional sense; it's gone to a place that can't process it.
Fix: This depends on the situation. If you sent to an exchange, contact their support immediately — they can sometimes recover cross-network deposits. If you sent to a personal wallet, you may be able to recover it by importing the receiving address into a wallet that supports both networks. This is preventable: always double-check you're on the correct network before sending. Our sending transactions guide has a pre-send checklist.
Cause 4: The Exchange Is Processing It
If you're withdrawing from an exchange, the transaction might be pending on the exchange's side, not the blockchain's. Exchanges run security checks, batch withdrawals, and sometimes manually review large transfers before broadcasting them. This can take anywhere from minutes to hours.
Fix: Check the exchange's status page and withdrawal processing times. If it's been more than 24 hours and the transaction hasn't appeared on the blockchain at all, contact their support.
What NOT to Do
- Don't send the same transaction again — you'll just create a second pending transfer. If the first one confirms, you've now sent twice.
- Don't panic and close your wallet — your transaction is on the blockchain regardless of whether your wallet app is open. It will confirm or drop based on network conditions, not your screen.
- Don't pay someone to "speed it up" — this is a common scam targeting people with stuck transactions. No third party can speed up a blockchain confirmation.
CGH Take: A pending transaction is almost always a fee or network issue, not a disaster. Identify which of the four causes applies, and the fix usually becomes obvious.