Binance Withdrawal Not Arriving? How Long a Withdrawal Takes
You hit withdraw, stare at the wallet for ten, twenty minutes, the other side still hasn't received it, and panic sets in. That feeling is completely understandable. But a withdrawal that hasn't arrived doesn't necessarily mean the money is lost; it may just be somewhere along the road. This piece teaches you to troubleshoot in order: first see what status it's in now, then judge whether to wait, check, or find someone. Get this chain of steps straight and you'll have your bearings.
01First read the withdrawal status: three meanings
The first step of troubleshooting is always to go back to "Wallet → Transaction History → Withdraw" in the Binance app, find that entry, and see what status it shows now. The status roughly falls into three types with completely different meanings, so don't conflate them.
Processing / Pending review. It means this withdrawal is still inside Binance and the platform hasn't broadcast the coins on-chain. New accounts, large amounts, or withdrawals that trip risk controls take a bit longer to review. Rushing at this stage does nothing, the block explorer can't find anything yet because the coins aren't even on-chain.
Sent / Pending confirmation. Binance has broadcast the coins; now it's up to the blockchain to process, waiting to be included in a block and for confirmations. At this point you can get a TxID (transaction hash) and track it on a block explorer.
Completed. From Binance's standpoint this withdrawal is done, the coins have gone on-chain and been sent to the address you entered. Note that "completed" is said from Binance's standpoint and isn't the same as "already visible in the other side's wallet"; there's still the receiving platform's crediting time in between.
This one step decides your direction: if the status is "Processing/Pending review," the problem is on Binance's side and all you can do is wait or contact support; if it's "Sent/Completed," the problem has moved to the chain or the receiving side, and what you do is check the TxID. Sort out which segment first, and you won't run around for nothing.
02Roughly how long each coin takes to arrive
A withdrawal generally goes through several stages before it arrives: Binance's review, inclusion in a block and confirmation on-chain, and then the receiving platform processing and crediting it. A transaction showing as successful on-chain doesn't mean the receiving platform's balance has been updated yet. Review time varies by person and amount; here's roughly how long the on-chain part takes, remembering it's always determined jointly by the protocol's characteristics and current congestion, so only a range can be given.
TRC20 USDT (TRON network): TRON produces blocks fast, so it usually arrives within a few minutes. Bitcoin BTC: a block roughly every ten minutes, plus several confirmations to wait, commonly from half an hour to an hour, longer when the network is congested. Ethereum ETH / ERC20 tokens: normally confirms within a dozen-odd minutes; when congested, fees are high and confirmation slow. BEP20 (BNB Chain): fast blocks, generally arrives fairly quickly too.
Why does the same kind of transfer differ so much by coin? The core is that each chain's block speed and the number of confirmations it requires differ. Fast-block chains (TRON, BNB Chain) naturally arrive fast; Bitcoin is slow because it produces a block only about every ten minutes, and the platform, for safety, often waits several blocks of confirmation before crediting you. This is a protocol characteristic, not Binance deliberately dragging things out, any platform receiving BTC has to wait this time. Once you understand this, you won't fret over a slow BTC withdrawal, slow is normal, and as long as the TxID is findable and it's confirming, it's on its way.
The above is just a rough range under normal conditions, not a promise. On-chain congestion, tighter platform review, or everyone transferring at once during sharp market moves all stretch the time. The exact arrival time and required confirmations follow what the Binance withdrawal page and the receiving platform show right now, so don't apply a fixed number. What you should really worry about isn't "slow," it's the "wrong entries" in the next section.
By the way, different chains differ not only in speed but in fees too. Think through which chain to use before withdrawing; you can first read how to pick TRC20/ERC20/BEP20, and whether a wrong-chain transfer can be recovered, or use the chain-choice tool to compare.
03A few common reasons it hasn't arrived
If it really keeps not arriving, run down the causes and see which one you hit.
You chose the wrong network. The same USDT has several chains, TRC20, ERC20, BEP20, and the chain you pick when withdrawing must match the chain the receiving side supports. Withdraw to an address that doesn't support that chain and the coins end up in an awkward state, possibly requiring a manual process to have any chance of handling.
Wrong address or memo/tag. If the funds have already been withdrawn from your account to a wrong address, Binance's self-service recovery page says it is unable to assist. Also watch for address poisoning: don't copy an address from your transaction history, and after pasting, check the whole address — MetaMask's guidance on poisoning scams says to pay close attention to the middle characters, not just the start and end. And some coins (say XRP sent to certain exchanges, or certain coins on some platforms) need a memo or tag in addition to the address; miss it or get it wrong and the receiving platform may not be able to match it to your account.
Not enough on-chain confirmations yet. The coins are already on-chain but haven't gathered the confirmations the receiving side requires, so it hasn't credited yet. This is just slow, not lost, keep waiting.
The platform is still reviewing. Back to section one, if the status is "Processing," it's not yet on-chain, so naturally it can't be found or arrive.
Many withdrawal mistakes can't be undone once you tap confirm, so do your checking before you tap it. Use copy-paste or a QR scan for the address rather than typing by hand; after pasting, check the complete address character by character; always pick the right network; and don't miss a required memo.
04Check the TxID on a block explorer to see where the coins are
As soon as the status reaches "Sent/Completed," you have a TxID to check. This is the most useful move, it settles for good whether the coins arrived and which address they reached, no guessing.
The steps are simple. In that withdrawal's details, find the TxID (transaction hash, a long string), copy it, then paste and search on the right chain's block explorer: for TRON (TRC20) use Tronscan, for Ethereum (ERC20) use Etherscan, for BNB Smart Chain (BEP20) use BscScan, and for Bitcoin use a mainstream BTC block explorer.
When it comes up, look at the transaction status first: Success means the on-chain part has gone through; Pending means it's still waiting to be included in a block; Fail means the transaction didn't execute and the coins weren't sent.
Only after the status do you check the address, and there's an easy misreading here: the To field doesn't mean the same thing for a plain ETH transfer and for a token like USDT. When ETH is sent directly, the top-level To is the recipient. When USDT is sent, the sender is actually calling the USDT token contract, so the top-level To is a contract address, not the recipient, and the explorer often labels it with the token name, such as Tether USD. The real receiving address and amount are in the token transfer details listed separately on the page; Etherscan calls these Token Transfers and shows them apart from ordinary ETH transfers. The ethereum.org documentation on the ERC-20 token standard spells it out: a token transfer calls the contract's transfer function, with the receiving address and amount passed as parameters of that call. Compare only the top-level To with the address you entered and they won't match, which can make it look as if the coins went to the wrong place. For TRC20, likewise go by the token transfer record in the explorer, and don't mistake the contract address for the receiving address.
Here's how to read an ERC20 USDT withdrawal (a teaching example; the addresses and amount below are made up):
- Transaction status: Success. The on-chain part has gone through.
- Top-level From: 0x5a3E…c81D. The address that sent the transaction, i.e. the address the coins left Binance from. It isn't yours.
- Top-level To: 0x7c2F…e90A, labelled Tether USD. This is the USDT contract address; it's normal for it not to match the receiving address you entered.
- Token transfer details: From 0x5a3E…c81D → To 0x9B47…2d6E, amount 100 USDT. This To is the receiving address. Check this complete address character by character against the receiving address in your Binance withdrawal record, then check the coin and the amount.
- Confirmations. The page shows the block the transaction is in and how many blocks have been added since. The receiving platform credits it only once it reaches the number of confirmations that platform requires; how many that is is in the receiving platform's deposit instructions.
Having read those fields, keep two things apart: successful on-chain and credited by the platform are two separate stages. If the status is Success and the receiving address and amount in the token transfer details match, the on-chain part is done and the coins have reached that address; if the receiving side is an exchange, it still has to confirm and record the deposit itself before it shows in your balance. If it hasn't arrived at that point, take the TxID to the receiving platform. If instead the status is Fail, the coins didn't reach the receiving address and the problem is on the sending side, so go back to the status in your Binance withdrawal record, or take the record to Binance support. If you can't find the transaction with the TxID, first check that you're using the explorer for the right chain and that you copied the whole TxID; if it still can't be found, go back to the status in your Binance withdrawal record and contact Binance support. If the receiving address in the token transfer details isn't the one you meant to send to at all, the address was most likely entered wrong.
It's fine if you can't make sense of everything the block explorer shows; look at three things in this order: the transaction status first; for a token like USDT, skip the top-level To and look at the To and amount in the token transfer details; and finally the confirmations. Etherscan has its own explanation of the difference between a plain transfer and a token transfer: Understanding an Ethereum Transaction. Learn this TxID-check move and you can get a first read on future deposit or withdrawal problems yourself, instead of just waiting around.
05Match your situation to the fix
Putting the above together, go by what you found:
Status still Processing/Pending review → nothing on-chain to check, wait patiently; if it's well past the usual time and still not moving, report through the official Binance support entry with a screenshot of the withdrawal record.
Status Sent, block explorer shows pending → just confirming, keep waiting; for a slow chain like BTC this is very normal.
Block explorer shows successful and the receiving address is correct (for a token, the To in the token transfer details) → the on-chain part is done and the coins reached the other side's address; what's left is the receiving side crediting it. If the receiving side is another exchange, wait for it to credit, and if it's taking far too long, contact its support with the TxID.
Block explorer shows failed → the coins didn't reach the receiving address; go back to the status in your Binance withdrawal record and take the record to the official Binance support.
The TxID can't be found in the explorer → first check that you're using the explorer for the right chain and that you copied the whole TxID; if it still can't be found, go back to the status in your Binance withdrawal record and contact the official Binance support.
Wrong network or wrong address/memo → immediately contact the receiving platform's support to explain, and see whether they can help recover, but be mentally prepared: many cases can't be recovered, especially an entirely wrong address.
Speaking of contacting support, one reminder: stick to the support entry you reach from the official Binance website or the official app. Those people on social platforms or in search results who proactively message you, claim to be "Binance support," and offer to "speed up the arrival" or "unfreeze the withdrawal" should all be treated as scammers, real support never reaches out to you first, and never asks you to transfer money or read out a verification code. However urgent a slow withdrawal feels, don't grasp at quack remedies and get scammed. For how to tell real from fake, see how to spot fake exchange apps and phishing sites.
So the order of checks is: read the withdrawal status first to tell whether the coins are still with Binance or already on-chain; then use the TxID to see the on-chain result; if it succeeded on-chain, go to the receiving side, and if it isn't on-chain or it failed, go to Binance.
Binance's official explanations of withdrawal status, arrival time, and recovery flow follow the current pages of the official Binance Help Center. For the complete withdrawal operation and what to watch, go through the complete withdrawal guide. If what you've hit is the reverse, a deposit not arriving, see the companion piece what to do when a Binance deposit doesn't arrive.
FAQFrequently asked questions
How long does a Binance withdrawal usually take to arrive?
It generally goes through several stages: Binance's internal review, inclusion in a block and confirmation on-chain, and then the receiving platform processing and crediting it; success on-chain doesn't mean the receiving platform's balance has been updated. For the on-chain part, TRC20 USDT usually arrives within a few minutes; BTC, with a block about every 10 minutes plus several confirmations, commonly lands in roughly 30 minutes to an hour; ETH/ERC20 is mostly within a dozen-odd minutes, all varying with on-chain congestion. If the status is still processing or pending review, that means Binance hasn't released it yet, which isn't a chain issue.
It shows completed but the other side hasn't received it. Where did the coins go?
Showing completed means Binance has broadcast the coins on-chain, and the rest is up to the blockchain. Copy that withdrawal's TxID (transaction hash) and check it on the right chain's block explorer, for example Tronscan for TRON, Etherscan for Ethereum. When the transfer is a token such as USDT, the top-level To is the token contract address, not the recipient; the receiving address and amount are in the token transfer details. If the explorer shows the transaction successful and the receiving address in those details is exactly the other side's address, the coins really did reach that address and the on-chain part is done; if the other side still hasn't credited it, take the TxID to the receiving wallet or platform rather than going back to Binance. If it shows failed, or you've checked the network and the TxID and still can't find the transaction, then go back to the status in your Binance withdrawal record and contact Binance support.
If I entered the wrong address or picked the wrong network, can the coins be recovered?
It depends, and often it's hard to recover. An entirely wrong address, with coins going into an address someone else controls, basically can't be recovered. A wrong network, but where the address happens to work on both chains and the receiving side is an exchange that supports that chain, may be recoverable with help from the receiving platform's support, but it goes through a manual process, depends on their policy, and isn't guaranteed. So before withdrawing always check the complete receiving address character by character, then check the network and the coin, since a mistake here is costly.