A Bitcoin transaction cannot partly fail. Either a miner put the whole thing in a block, or it moved nothing at all. When something says failed, it means one of seven things: nodes rejected it at broadcast, it was dropped after waiting too long, it was replaced by a higher fee version, a conflicting transaction won, it was never broadcast, it was a Lightning payment that found no route, or an exchange stopped its own withdrawal. In every case except a replacement that paid someone, the coins are still with the sender, and the wallet only needs to catch up.
The word failed does a lot of damage in this corner of the internet. People see it next to a payment, assume the money is gone, and start searching for help at exactly the moment the scammers are waiting. So the first thing to know is the most useful one: on the Bitcoin network itself there is no failed. A transaction is a single signed instruction. It is either confirmed in a block, all of it, or it has not happened, none of it. There is no state in between where the coins left and did not arrive.
What you are looking at is a label applied by software. Different wallets, exchanges and explorers use it for different events. Find out which event, and you know where the coins are.
The seven things failed can mean
| What happened | Where you usually see it | Where the coins are |
|---|---|---|
| Rejected at broadcast | An error the moment you press send | Still in your wallet. Nothing left |
| Dropped | Wallet history, days after sending | Back in your wallet once it rescans |
| Replaced | Explorer banner, wallet history | Wherever the replacement sent them |
| Conflicted | Bitcoin Core, some explorers | Wherever the winning transaction sent them |
| Never broadcast | Wallet shows sent, explorers show nothing | Still in your wallet |
| Lightning payment failed | Lightning wallets | Still in your Lightning balance |
| Exchange withdrawal failed | Coinbase, Binance, Cash App and others | Back in your exchange balance |
Five of the seven end with the coins exactly where they started. The two that do not, replaced and conflicted, both mean another transaction confirmed instead, and that transaction is public, so you can see precisely where the money went. The sections below take each in turn.
Ask twenty nodes what they see
Paste the transaction ID. We report whether it is confirmed, waiting, or unknown to every node, which tells you which row of that table you are in.
Rejected at broadcast
The wallet signed the transaction, offered it to a node, and the node said no. Good wallets show the node's reason. These are the ones you will meet, in the exact words nodes use.
| Message | What it means | Fix |
|---|---|---|
| min relay fee not met | The fee rate is below that node's minimum, 0.1 sat/vB by default | Resend at a higher rate |
| mempool min fee not met | The node's mempool is full and is turning away the cheapest offers | Raise the rate above the current floor |
| insufficient fee | You sent a replacement that does not pay enough more than the original | Pay more in total, plus the relay increment |
| txn-mempool-conflict | Another waiting transaction already spends the same coins | Replace it properly, or wait to see which confirms |
| bad-txns-inputs-missingorspent | The coins were already spent, or the parent is unknown to this node | Check whether an earlier version confirmed |
| dust | An output is so small it would cost more to spend than it is worth | Send a larger amount |
| non-final | The transaction has a lock time in the future | Wait until that time, or rebuild without it |
In every case nothing left your wallet, because the network never accepted the transaction. Some wallets show the coins as reserved for a while; a restart or rescan clears that. The commonest one in 2026 is the first: a wallet whose economy setting falls below what strict nodes accept. Our fee calculator shows the live floor and a rate that clears.
Dropped
The transaction was accepted and waited, but it paid too little to be mined, and nodes eventually let it go. Most discard an unconfirmed transaction after 336 hours, fourteen days, and a node whose mempool fills up evicts the lowest payers sooner. Once enough nodes forget it, it no longer exists anywhere that matters. Some wallets then mark it failed; others leave it pending forever until you tell them otherwise.
The coins never moved, so they are yours to spend again. If your wallet still shows them as sent, it needs a nudge: in Bitcoin Core right click the transaction and choose Abandon transaction, which is only offered once it is out of the mempool; in Electrum a transaction that never confirmed and is no longer known can be removed from history. The vanished transaction guide covers rebroadcasting it instead, if you still want that payment to go through.
Replaced
Someone signed a newer version of the transaction spending the same coins with a higher fee, and nodes swapped it in. That someone is almost always the sender: a fee bump, a cancel, or a wallet that rebroadcast with a new fee on its own. mempool.space shows the original with a banner saying it was replaced, and a link to the replacement.
Follow the link. The replacement is the transaction that matters. If it pays the same recipient, the payment happened, just under a different transaction ID, which is why a receiver can see failed on one ID and confirmed on another. If it pays the sender back, the payment was cancelled. Either way, the outputs of the replacement tell you exactly where every coin went.
The new transaction ID catches people out
A replaced payment has a new ID. A seller or exchange watching the old ID will see it fail and may tell you the money never arrived. Send them the replacement's ID. It is the one in the block.
Conflicted
Close to replaced, but from the other side. Two transactions spent the same coins and the other one confirmed. Bitcoin Core labels the loser conflicted and shows it with negative confirmations. It happens after a cancel or bump made from another wallet holding the same keys, after a wallet restored from backup rebuilt an old payment, and in deliberate double spends against someone who accepted a payment before it confirmed.
If you were the receiver and the payment shows conflicted, the sender's coins went somewhere else, and the money is not coming through that transaction. That is the risk of accepting an unconfirmed payment for anything valuable, and the reason merchants wait for a confirmation.
Never broadcast
The wallet built and signed it but never got it to a node: a dropped connection, a server that was down, a firewall. Electrum calls such a transaction local. Explorers have never seen it. Nothing happened, and the fix is either to broadcast it now or to delete it and send again. Pushing a transaction explains how, and the not found guide helps confirm this is your case rather than a typo or the wrong chain.
A Lightning payment failed
Lightning payments travel through a chain of channels, and failed there means no route with enough capacity was found, or a node along the way did not forward it in time. The payment either completes for everyone or for no one, so a failure leaves the balance where it was. Occasionally a payment stays in flight for a while before resolving; the funds are locked, not lost, and come back when the attempt times out. Retrying with a smaller amount, a different time, or a wallet with better channels usually works.
An exchange withdrawal failed
Exchanges run their own queues before anything reaches the network. Failed or cancelled there usually means a compliance check, a wrong network selected for the destination, an address the exchange refused, or a hold on the account. If the withdrawal never got a Bitcoin transaction ID, the network was never involved, and the exchange returns the balance to your account. If it shows a transaction ID that later failed, it was dropped or replaced, and the exchange has to deal with it on its side. In both cases support needs the withdrawal reference, and the exchange guide lists what each platform shows.
Where did the money go: the four question check
- Does any explorer find the transaction ID? No: it was never broadcast or it was dropped. The coins are with the sender.
- Is it confirmed? Yes: it did not fail, whatever a label says. The payment happened.
- Does the explorer say replaced, or conflicted? Yes: open the transaction that won. Its outputs are where the coins went.
- Is it still waiting? Then it has not failed at all. It is pending, and probably underpaid. The fee bump calculator shows what lifting it costs.
When the balance still looks wrong
Wallets keep their own records and sometimes lag behind the network. If the check above says the coins never moved but the wallet disagrees, make it look again: Bitcoin Core can rescan the chain, Electrum rebuilds its history when it reconnects, and most mobile wallets have a refresh or resync option. What you should never do is enter your recovery phrase into a website or app that offers to find failed funds. That is not a recovery. It is the theft.
The bottom line
Failed is a label, not a Bitcoin event. Work out which of the seven it means by looking the transaction up, and in five cases you will find the coins never left. In the other two another transaction confirmed instead, and it is sitting on the blockchain for anyone to read, outputs and all. The only failed transaction that ever costs money is the one followed by trusting a stranger to fix it.
Find out which one you have
Paste the transaction ID. Confirmed, waiting, replaced or unknown to twenty nodes, in a few seconds and for free.
Frequently asked questions
What does it mean when a Bitcoin transaction failed?
Bitcoin itself has no failed state: a transaction is either confirmed in a block or has moved nothing. A failed label means nodes rejected it at broadcast, it was dropped after waiting too long, it was replaced by a higher fee version, a conflicting transaction confirmed instead, it was never broadcast, it was a Lightning payment that found no route, or an exchange stopped the withdrawal.
If a Bitcoin transaction failed, where is my money?
In most cases still with the sender. A rejected, dropped or never broadcast transaction never moved any coins, and a failed Lightning payment or exchange withdrawal returns to the balance. If it was replaced or conflicted, another transaction confirmed instead, and its outputs on any explorer show exactly where the coins went.
Why does my Bitcoin transaction say replaced?
Someone, usually the sender, signed a newer version spending the same coins with a higher fee, to speed it up or to cancel it. The replacement has a new transaction ID. Open it on an explorer: if it pays the same recipient, the payment went through under the new ID.
What does conflicted mean in Bitcoin Core?
Another transaction spending the same coins confirmed, so this one can never confirm. Bitcoin Core shows it with negative confirmations. It follows a cancel or bump made elsewhere with the same keys, a wallet restored from an old backup, or a deliberate double spend.
What does min relay fee not met mean?
The fee rate is below the minimum the node accepts, 0.1 sat/vB by default since Bitcoin Core 29.1 and higher on some nodes. Nothing left your wallet. Resend at a higher rate.
Can a failed Bitcoin transaction take my money?
No. A transaction that did not confirm moved nothing, and a failed Lightning payment completes for no one. The only way money is lost after a failed transaction is by giving a recovery phrase or a fee to someone who claims they can recover it.
How do I fix a Bitcoin transaction stuck as failed in my wallet?
Check the transaction ID on an explorer first. If it is unknown to the network, make the wallet forget it: Abandon transaction in Bitcoin Core once it is out of the mempool, or removing the local transaction in Electrum, then rescan or resync. The coins become spendable again.