Withdrawal not arrived? Take the TxID to a block explorer and find out

Late one evening a friend pinged me, clearly rattled: "I withdrew some USDT from Binance to another wallet, it's been over half an hour and still nothing, has it been swallowed?" I told him to stop guessing and send me the transaction hash for that withdrawal. One look it up on a block explorer and the status was written plain as day, on-chain, arrived, done. He just hadn't refreshed the new wallet and was still staring at the old balance. He reopened the app, pulled to refresh, and the money was sitting right there.

When a withdrawal "hasn't arrived," genuinely lost coins are the rare case. Far more often it's just the surface of things: not refreshed, not enough confirmations yet, or you simply checked the wrong place. This piece walks you through a check you can run yourself: first work out where it went, then use the transaction hash to look up exactly what happened on-chain, read the confirmations, and finally tell apart a false alarm from a real problem.

First split it: to another exchange, or to an on-chain wallet

Step one is always to work out where the money was actually sent, because the two cases are checked completely differently:

• To another exchange or platform: the money lands in their deposit address, and whether it shows up is also subject to their crediting rules. On-chain arrival doesn't mean they'll display it instantly, they may still run their own confirmation and crediting process.
• To your own on-chain wallet (MetaMask, a hardware wallet, etc.): the money goes straight to an on-chain address, and arrival depends entirely on the status of that on-chain transaction. This is the case best suited to checking yourself on a block explorer.

Telling these apart saves you a mountain of fruitless hunting. If it doesn't show at the other platform but the chain says "arrived," the place to ask is the other platform, not Binance.

What a TxID is, and where to find it

The TxID (Transaction ID, the transaction hash) is the "ID number" of every on-chain transfer, a long string of letters and digits, unique across the whole network. With it, you can look up all the public status of that transaction on a block explorer: the sending and receiving addresses, the amount, the time, the confirmation count, success or failure. After a withdrawal succeeds, open that entry in your withdrawal history and you'll usually see a "transaction hash / TxID" field with a copy button beside it. Copy it and take it to the explorer.

Pick the lookup site by the chain your withdrawal went out on:

• If it went via Tron (TRC20), check it on Tronscan.
• If it went via Ethereum (ERC20), check it on Etherscan.
• If it went via BSC (BEP20), check it on BscScan.

Pick the wrong explorer for the chain and your hash won't show up on it, that's not lost coins, it's knocking on the wrong door.

Hands-on: tracing a withdrawal for a friend

Take that evening as the example. My friend's went via TRC20, so I went to Tronscan. The whole thing is actually simple:

1. Open Tronscan, paste the transaction hash he sent me into the search box at the top, and hit enter.
2. The transaction's details come up. I look at the status at the very top first, it shows success (a green Success / Confirmed). That one glance rules out "transaction failed."
3. Next I check the sending address, receiving address, and amount. The receiving address matches the one he pasted me character for character, and the amount lines up too. By here I'm basically at ease, the money really did go to the right place.
4. Finally I look at the confirmations and the time. Confirmations were long past enough, and the time showed a few minutes earlier. In other words, this one finished on-chain ages ago.

After checking I told him: everything on-chain is fine, the money's at your address, go refresh your wallet. He reopened the app and, sure enough, the balance was there. The whole frantic half hour came down to not refreshing plus not knowing how to check it himself. Learn this one move and you can diagnose this kind of "didn't arrive" yourself from now on.

What "confirmations" are actually waiting for

When you check a transaction you'll often see "confirmations X / N." This is where beginners get most anxious, it's on-chain already, so why keep waiting? Put simply: a transaction being packed into a block is just the "first confirmation," and each new block mined after that adds one more. The more confirmations, the more irreversible and secure the transaction, so the receiving side usually requires a certain number before crediting you. It's a protection against rollbacks, not a deliberate delay.

Different chains produce blocks at different speeds, so the time to stack up enough confirmations differs too. Here I'll stick to protocol-level basics, not pinning down exact arrival minutes:

• Tron (TRON): roughly one block every 3 seconds, so TRC20 transfers are usually quick and confirmations stack up fast.
• Ethereum: roughly 12 seconds per slot (its block cadence), and it's also affected by congestion and gas, so it's slower when busy.
• BSC: blocks come fast too (on the order of about 3 seconds per block), so confirmations usually aren't slow.
• Bitcoin: roughly one block every 10 minutes, so waiting for confirmations is naturally slower than the chains above. That's a property of the protocol.

So if your status says "pending," don't panic, glance at how many confirmations it's waiting on and which chain it's on, and you'll have a feel for it. Exactly how many confirmations you need and how long that maps to goes by the receiving platform's rules and what the block explorer shows at that moment (checked as of 2026-06).

The three situations where coins really can be lost

Most of what's above is a false alarm. But there are three situations where coins genuinely can become unrecoverable, which is exactly why you have to check carefully before transferring:

• Wrong network (chain). The same coin often supports several chains. If the chain you picked for the withdrawal doesn't match the chain the receiving side supports (say they only take TRC20 and you sent on ERC20), the coins may never reach their account, and recovery is extremely difficult or impossible. The networks on both ends must match, this is the number-one iron rule.
• Wrong address. Once an on-chain transfer is broadcast and confirmed, it's irreversible. One wrong character in the address and the coins go to an address you don't know, basically gone for good. Always copy and paste, then check digit by digit, never type it by hand.
• Missing memo / tag. Some coins require a memo (a note / tag) when transferring into an exchange. Miss it or get it wrong and the coins are on-chain but can't be credited correctly to you, so you have to go through the receiving side's recovery process, and whether you get them back depends on their policy.

How long arrival takes, and what it depends on

"How long until it arrives" has no fixed answer, because it's shaped by several things at once: which chain it's on (Tron and BSC produce blocks fast so they're usually quick, Bitcoin at roughly one block per 10 minutes is naturally slow), how many confirmations the receiving side requires, whether the network is congested (Ethereum slows noticeably at peak times), and the receiving side's own crediting pace.

So the right mindset is: use the TxID first to confirm the on-chain transaction succeeded and that the address and amount are correct, and the rest is just patiently waiting out the confirmations. If it's succeeded on-chain, confirmations are enough, and the other side still isn't showing it, then go ask the other platform. Exact timing always goes by what the block explorer and the receiving platform show at that moment (checked as of 2026-06), don't argue with stale numbers off the internet.

A few questions asked to death

Binance shows the withdrawal as "completed," but the money's not here, what's going on?

"Completed" generally means Binance has already broadcast the transaction on-chain. After that it comes down to on-chain confirmations and the receiving side's crediting. Take the TxID to the matching block explorer and check the status; if it's succeeded and the address and amount are correct, it's usually that confirmations aren't enough yet or the other side isn't showing it, so refresh and wait, or ask the other platform.

I checked the TxID and the block explorer can't find it, is it lost?

First confirm your explorer matches the chain, TRC20 goes to Tronscan, ERC20 to Etherscan, BSC to BscScan. Wrong explorer and naturally it won't show. If the chain's right and it still won't appear, the transaction may not have broadcast yet, wait a bit and check again.

Wrong address, or wrong chain, can I still get the coins back?

On-chain transfers are irreversible. A wrong address, or sending to an address that doesn't support that chain, makes recovery extremely difficult or impossible. In some cases, if the receiving platform supports that chain and can help consolidate it, you go through their recovery process, depending on their policy. The core thing is to check the address digit by digit and match the networks on both ends beforehand, never type it by hand.

I forgot the memo / tag, what now?

The coins are usually on-chain but not credited correctly to the other side. You'll need to contact the receiving platform and provide proof such as the TxID through their recovery process, with recovery depending on their policy. Next time, don't miss the memo where one's required.

---

When a withdrawal doesn't arrive, don't jump to the worst case. Step back: work out where it went, look up the TxID, read the confirmations, and most "didn't arrive" turns out to be a false alarm once you've checked. The ones that are real problems come down to a wrong network, a wrong address, or a missing memo, and those are all prevented by checking before you transfer. Learn this on-chain check and you'll be able to settle this kind of thing yourself. Once this transfer goes smoothly and you feel at ease, if you don't have a Binance account yet and plan to open one, you can register with invite code BN4001 for a 20% trading-fee discount^*. * Actual rate shown on Binance, subject to change.