Confirmations done but the deposit isn't credited: a step-by-step check

The confirmation count on the explorer sailed past what Binance asks for — doubled it, even. You've refreshed a dozen times, the status reads success, and your Binance balance still hasn't moved. This kind of stuck rattles you more than "not enough confirmations yet" — you've waited out everything you were supposed to, and the coins still haven't shown.

Keep two situations apart. If your confirmations are actually still a few short, that's a different story — just keep waiting; the sibling piece how long a deposit takes covers the per-network ballpark and the why. This one handles a single case: the confirmations genuinely are enough, past the requirement even, and Binance still hasn't credited it. Here's how to pin down where the problem sits, one item at a time.

First, make sure "enough confirmations" is really true

Before you go hunting for a fault, nail down the premise itself. A fair number of people who think they're stuck have actually misread this part — the number looks right, but they compared it to the wrong thing.

The catch: the required confirmations differ for every coin on every network. The same USDT can need a very different count on Tron versus Ethereum. So the current confirmation count you see on the explorer has to be compared against what Binance's deposit page shows for that specific coin on that specific network — not against some round number in your head. When you think it's "enough," you might just be measuring against the wrong figure.

While you're at it, check two more things. The status on the explorer should read success — some transactions land on-chain but fail on execution, so there's a record yet nothing really went through. And the destination should be your current deposit address — the one the page generated for this deposit, not one you screenshotted ages ago. Required confirmations, status, address: only once all three line up can you say "enough but not credited." For a rough sense of what each chain needs, see the confirmations reference by chain; the final word is whatever Binance shows at deposit time.

Enough confirmations, still not credited — usually one of these

With the premise settled and still nothing credited, the cause is most likely on this list — each with a quick way to tell, so no need to panic. The full self-rescue for each lives in the deposit and withdrawal mistakes roundup; here we just help you spot which one it is.

• The exchange still has an internal crediting step. A gap in the first little while after the count is met doesn't automatically mean trouble — confirmations landing on-chain doesn't mean the exchange instantly books the coins to your name; there's an internal queue to clear first. Give it a reasonable buffer and check again; plenty of "stuck" deposits sort themselves out.
• A required memo / tag was left off. Some coins — certain platform tokens, and chains that use a tag to tell accounts apart — require a memo to deposit to an exchange. Leave it off and the coins reach the chain, but nothing tells the exchange whose account to credit, so it won't post automatically and you're into a recovery process. Whether a missing memo can be recovered, and how long that takes, depends on the coin and the platform's policy — it isn't guaranteed. For how to handle it, see what to do about a missing memo.
• Wrong network, or the destination isn't your deposit address at all. The network you sent on isn't the one your copied deposit address belongs to — or the address simply isn't yours. Either way the coins can't reach your account. For how to tell and whether you can rescue it, see wrong network — are the funds safe?
• You used an old, deactivated deposit address. Addresses get retired when a coin or the system changes, so depositing to one you saved long ago can mean the coins never reach your current account. Go by the address Binance shows fresh this time; don't reuse an old one to save a step.

The last two are easier to judge, but they're also the ones people skip past:

• Deposits for that coin and network are suspended, or the wallet is under maintenance. Every so often an exchange temporarily pauses deposits for a coin or network, or does wallet maintenance, and coins arriving during that window get held. Check that coin's deposit page and Binance's announcements for a notice.
• Below the minimum deposit. Every coin has a minimum on every network, and sending too little can mean it never posts. Go back and check your amount didn't slip under that line — details in minimum deposit.
• This particular deposit got flagged for review (under review). A single deposit occasionally gets an extra review — a normal risk-control mechanism. No clever shortcut here: have your details ready and contact Binance's official support to cooperate with the check. Ignore anyone online telling you how to "dodge the review" or "get around risk control" — that only makes it worse.

Check it yourself, in order

Knowing the possibilities isn't enough; you need a fixed order to check them, or you'll skip one. Walk this and it goes smoothly:

1. Take the TXID to the block explorer and check four things. Find the transaction's hash (TXID) in the wallet you sent from, pick the right explorer — Tronscan for Tron, Etherscan for the Ethereum family, BscScan for BSC — and look up: is the status success; has the confirmation count actually reached or passed Binance's requirement for that coin and network; is the destination your current deposit address; and for tag-based coins, was the memo included correctly.
2. Go back to Binance's deposit page and announcements for that coin. Confirm whether deposits for this coin and network are paused or the wallet is under maintenance right now, and exactly how many confirmations are required — don't borrow another coin's number.
3. Everything lines up and it still hasn't arrived? Then use the official query. Get the TXID, network, destination address, amount and rough send time together, and submit them through Binance's official support or self-service query. Don't DM anyone off-platform claiming to be "support" — use only the channel inside the Binance app or on its own pages; impersonators love a moment when you're anxious. If it turns out to be a missing memo or a wrong-network transfer, follow the matching recovery process — and again, whether these can be recovered isn't guaranteed, and some cases are irreversible.

FAQ

Sources: Binance Help Center, Tronscan, Etherscan, BscScan. Required confirmations and arrival times are live data — whatever Binance's page and the block explorers show at the time.