A stablecoin transfer that looks stuck or missing is almost always in one of a few states, and a block explorer plus your transaction ID will tell you which. Diagnosing that state comes first. Only once you know whether the transfer is pending, confirmed, failed, or gone to the wrong place can you pick the right next step.
The reassuring part is that most transfers that look lost are not lost. They are usually still pending, or already arrived somewhere you are not looking. The rarer, harder case is a transfer sent to the wrong network or address. If the basics of moving stablecoins across networks are still fuzzy, that guide sets up everything here.
Work through it in order, and you avoid both needless panic and the wrong fix.
Start with the transaction ID
Every stablecoin transfer leaves a receipt: a transaction ID, also called a hash. It is a long string that your sending app records the moment you approve a transfer. Finding it is the first step, because almost every other check starts from it. No transaction ID at all often means the transfer never left.
A stablecoin moves value on a digital ledger, a shared record book of who holds what (source: Bank of England stablecoin explainer), and each move is written into it with its own ID. You will find it in the transaction or withdrawal history of the app or exchange you sent from. Copy the full string, since a missing character makes it impossible to look up. The ID is unique to that one transfer, so it points to a single record no matter how many transfers you have made. That is what makes it the fastest way to learn what happened. If your app also shows a status like sent or complete, note it, but treat the explorer as the real check.
If there is no ID at all, treat that as a clue, not a disaster. It usually means the send never broadcast to the network. The most common reason is that the wallet held no fee coin, so the transfer could not start. In that case nothing left your balance, and the fix is on the sending side rather than out on the network. The mechanics of making a send in the first place are covered in sending and receiving crypto. Either way, the ID, or its absence, is the thread you pull first.
Read it on the right network's explorer
A block explorer is a free public tool that shows any transfer's status from its ID. The important word is right: you must use the explorer for the network you actually sent on, because each network has its own. Paste the ID in, and it shows whether the transfer is pending, confirmed, or failed, and the addresses involved.
The explorer reads the network's own ledger, so it is the source of truth, not your wallet's display. A wallet can show stale data, but the ledger does not. A transfer is broadcast, then included in a block, and later settled as final (source: Ethereum transactions and finality), and the explorer shows you exactly where in that path your transfer sits. A wallet may still show a spinner or an old balance while the ledger has already settled, so trust the explorer over the screen in front of you.
Using the wrong network's explorer is the single most common reason an ID seems "not found." A transfer sent on one network will never appear on another network's explorer, even though the coin's name is the same. So if a lookup comes back empty, check the network before you conclude anything is wrong. The full walk through an explorer's fields is its own guide to reading a block explorer. What matters here is simpler: the explorer, not the app, tells you the true state. So the very first move, before contacting anyone, is to look the transfer up yourself. The answer is usually right there in the status field, and it decides everything you do next.
The four states, and what each means
Once you find the transfer on the explorer, it is in one of four states: not found, pending, failed, or confirmed. Each one points to a different next step, and telling them apart is the whole job of troubleshooting. Get the state right, and you stop chasing the wrong fix or contacting the wrong party.
Take them one at a time. Not found means the transfer never broadcast, so the fix is on your side, usually adding the network's fee coin and sending again. Pending means it was sent but not yet confirmed, which usually just means the network is busy or the fee was low; how fees drive that wait, and whether you can speed it up, comes down to network fee mechanics (source: Ethereum gas fees).
Failed means the network rejected it and the coins did not move, often for too little fee, and a failed transfer can still cost a small fee even though nothing transferred. Confirmed, or success, means the coins reached the destination address on that network, which is a matter of settlement and custody rather than something still in flight.
| Explorer state | What it means | Your next step |
|---|---|---|
| Not found | Never broadcast to the network | Fix on the sending side, then resend |
| Pending | Sent, not yet confirmed | Wait; it is usually congestion or a low fee |
| Failed | Rejected; coins did not move | Check the fee coin, then resend |
| Confirmed / success | Coins reached the destination address | Move to the next section if it still seems missing |
Success but the recipient can't see it
The confusing case is a confirmed transfer the recipient still cannot see. The explorer says success, so the coins moved, but they are not showing up. That almost always means they arrived somewhere slightly different from where the recipient is looking, not that they vanished.
There are a few usual reasons, and it helps to check them in order. The first is the wrong network. The same coin lives on several networks at once (source: Tether transparency), so the recipient has to look on the exact network you sent, not another.
The second is the wrong version. A bridged coin can arrive where a native one was expected. There it may sit unrecognized, and unlike a native coin it cannot be redeemed with the issuer (source: Circle, USDC vs USDC.e). The full native-versus-bridged split is covered in bridged versus native stablecoins. A bridge makes that stand-in by locking the native coin on one network and issuing a matching token on another (source: Circle Cross-Chain Transfer Protocol), so the two are not the same asset even when they share a name.
The third reason is the plainest of all. The recipient may simply not have added the coin or network in their app yet, so a coin sitting in a crypto wallet may need the network or token switched on before it shows. And if the destination is an exchange, the platform may just not have credited the deposit yet, which is a waiting matter for that platform rather than a fault in the transfer. Work down this short list before assuming a confirmed transfer is gone.
When it went to the wrong place
The hard case is a transfer that confirmed to the wrong address or the wrong network. Here the coins really did leave, and whether anything can be recovered depends on who controls the destination and whether the coin exists there at all. Often the honest answer is that it cannot be undone.
It helps to sort by where the coins landed. If they went to your own wallet on a network you can reach, you may be able to see them by switching your app to that network, which is a self-custody matter rather than anything this guide performs. If they went to an exchange deposit address, the platform may run a recovery process, so that becomes a question for its support rather than for you alone. If they went to a stranger's address, or to a network where the coin does not exist, they are usually not recoverable at all. There is no neat trick that reverses it, which is the honest and important part.
Two rules hold across every version of this. A confirmed transfer cannot be reversed by anyone, so no support line can simply pull it back. And you should never send more coins to the same address hoping to fix the first mistake, because that only adds a second loss. Where the coins sit in an exchange account or a wallet decides what, if anything, is possible next. So the realistic goal is to work out which case you are in, act quickly if a platform is involved, and accept the answer when the coins are genuinely out of reach.
What to gather before you ask for help
Whether you are contacting a platform or checking a wallet, the same evidence makes the difference. Gather it before you reach out, because a support team can act far faster with a complete picture than with a vague one. It is also what tells you whether help is even needed.
Here is the short list to collect from the explorer and your sending app:
- The transaction ID (hash) for the transfer.
- The exact network you sent on.
- The sending address and the receiving address.
- The amount, and the coin plus its version, native or bridged.
- The timestamp and the explorer's status for the transfer.
From BloFin's operational view, a deposit that already shows success on the explorer is on the chain, so the only thing left is for the platform to credit it. A platform does that fastest when your ticket includes the hash, the network, and the address, not just a screenshot. Where the destination is a platform, its own support owns that step, not this guide. Where it is self-custody, the safe path stays with crypto security basics: never share your recovery phrase, and ignore anyone who messages you offering to retrieve your funds for a fee, because that is a scam, not a service.
The best troubleshooting, of course, is the kind you never need. Sending a small test amount first, and choosing a network both sides support, prevents most of these cases outright. If the whole idea of moving a coin is still new, the hub guide to what a stablecoin is is the place to start.
Frequently asked questions
Should I contact the sender or the recipient's platform first?
Let the state decide, so you do not ask the wrong party. If the explorer shows the transfer as not found or failed, the problem is on the sending side, so the sender acts, usually by adding the fee coin and trying again. If it shows success, the coins have left, so the question moves to the receiving side, whether that is a platform that has not yet credited a deposit or a wallet that needs the right network switched on. Checking the state before you reach out saves everyone a round of the wrong questions.
Can I track a transfer if I only have the address, not the transaction ID?
Yes, though the ID is faster. Pasting the receiving address into the right network's explorer shows the transfers in and out of it, so you can usually find the one you are looking for by amount and time. The transaction ID jumps straight to the single transfer, which is why it is worth finding first. Either way, the explorer for the correct network is the tool. If neither the ID nor the address shows the transfer, that is a strong sign you are checking the wrong network.
Can I cancel or speed up a transfer after I have approved it?
Usually you cannot cancel it, and sometimes you can speed it up, depending on the network. Once a transfer is broadcast it is out of your hands, and if it has already confirmed, nothing cancels it. While it is still pending, some networks let you replace it with a higher fee to jump the queue, while others simply make you wait. How that replacement works comes down to gas mechanics, which the fee guide covers; it is not something you set up here. The safe assumption is that an approved transfer will go through, so check everything before you approve.
How many confirmations should a deposit have before I trust it?
It depends on the network and, for a deposit, on the platform receiving it. Each confirmation is another block added after your transfer, and more confirmations make it harder to reverse. A small everyday transfer is usually fine on the first confirmation, while a platform crediting a deposit often waits for a set number of its own before it releases the funds. That waiting count is the platform's rule, not a fault in your transfer, which is why a deposit can read as confirmed on the explorer yet still sit pending in the account for a while.
What if the recipient's address was meant for a different coin?
That is a real risk, because an address can be tied to a specific coin as well as a specific network. If you send one stablecoin to an address a platform issued for a different asset, it can end up unrecognized or stuck, much like a wrong-network send. The explorer will still show it reaching that address, so the coins did move, but whether they can be sorted out depends on who controls the address. Always take the deposit address from the page for the exact coin and network you are sending, not a general one.
Does sending a bigger amount make a transfer more likely to get stuck?
No. The amount does not decide whether a transfer confirms. What a transfer gets stuck on is the network and the fee, not the size of the payment, so a large transfer and a small one on the same network and fee behave the same way. A big amount is worth more care for other reasons, like double-checking the address and waiting for more confirmations before you rely on it. But the size itself does not make the network slower or the transfer more likely to fail.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated July 2026. Primary sources: the Bank of England, Ethereum.org, Circle, and Tether. All facts independently verified against cited documentation current as of July 2026.
This article is educational and general in nature, not financial, investment, tax, or legal advice. Stablecoin transfers are typically final and cannot be reversed, and coins sent to a wrong address or a wrong network are often impossible to recover; recovery is never guaranteed. Never share your wallet recovery phrase, and treat any unsolicited offer to recover funds as a scam. Nothing here is a recommendation to buy, sell, or hold any specific asset. Do your own research, follow the laws where you live, and consider a licensed professional before making financial decisions. BloFin does not provide investment advice.