Crypto Withdrawal Stuck on Pending? Check for a TXID First (2026)

Jump to a Section

• The One Check That Splits the Problem
• No TXID: It Is Still at the Exchange
• TXID Exists: It Is on the Chain
• The Mistakes That Are Not Delays
• When Is It Time to Open a Ticket?
• How to Make the Next One Not Do This

The One Check That Splits the Problem

Open your withdrawal history on the exchange and look at the individual record. You are looking for a long string of letters and numbers labelled TXID, transaction hash, or simply hash.

What you see	What it means	Who can fix it
No TXID	Funds have not been broadcast. They are still on the exchange.	Only the exchange
TXID present	Broadcast to the network. The exchange’s job is done.	The network, or the receiving side

This matters because the two halves have no overlap. If there is no TXID, searching a block explorer will find nothing and you will conclude something is badly wrong when the withdrawal is simply sitting in a queue. If there is a TXID, contacting support achieves nothing — they cannot speed up a blockchain, and a polite agent telling you to wait is the correct answer.

Paste the TXID into the explorer for the network you used: mempool.space for Bitcoin, etherscan.io for Ethereum, tronscan.org for Tron, solscan.io for Solana. If the explorer says the transaction does not exist, treat it as the no-TXID case.

No TXID: It Is Still at the Exchange

Four things hold a withdrawal at this stage, roughly in order of how often they are the answer.

Automated risk review. Most exchanges run withdrawals through a screening step, and a transaction can be pulled for manual review without you being told. Common triggers are a first-time withdrawal address, an unusually large amount relative to your history, a login from a new device or country, or a recent change to your password, email or two-factor settings. Several exchanges apply a fixed hold — often around 24 hours — after a security-setting change specifically to blunt account takeovers. If you changed anything on the account recently, that is very likely your answer, and waiting is the fix.

Verification tier or limits. Withdrawal allowances are tied to verification level and reset on a daily cycle. If your request crosses your daily cap it can sit rather than fail outright, and a partially used allowance earlier in the day counts. Check your remaining limit for the day rather than your total limit.

Incomplete or expired KYC. Documents can lapse, or a previously accepted verification can be re-requested when rules change in your region. This usually surfaces as a notification you have not read rather than an error on the withdrawal itself.

Exchange-side maintenance on that specific asset or chain. Wallet maintenance is normally per-network, so USDT on Tron can be suspended while USDT on Ethereum is fine. Exchanges publish this on an announcements or system-status page, and it is worth checking before assuming the problem is your account.

TXID Exists: It Is on the Chain

Once broadcast, the exchange has no further control. What you are waiting on is confirmations, and there are only a few reasons they are slow.

Network congestion and fee level. Blocks have limited space and transactions compete on fee. When a network is busy, anything paying a below-market fee waits — sometimes hours. The explorer will show your transaction as unconfirmed and in the mempool. Exchanges set the fee themselves, so you cannot bump it, and Bitcoin transactions from exchanges are frequently batched, which adds latency before broadcast but does not affect confirmation once sent.

The receiving side needs more confirmations than you expect. This is the most common false alarm. The chain shows your transaction confirmed while the destination still shows nothing, because the receiving exchange or service waits for its own threshold before crediting. Thresholds vary by asset and by platform, and a service can raise them temporarily during unstable conditions. If the explorer says confirmed and the destination does not, the delay belongs to the destination.

Chain-level problems. Rarer, but real. A network can halt or fork, and during such events explorers may show inconsistent states. Nothing productive is available to you here beyond waiting for the network to resolve.

Explorer shows	Destination shows	What to do
Not found	Nothing	Treat as no-TXID — the exchange still holds it
Unconfirmed / pending	Nothing	Wait. Fee and congestion. Nobody can speed it up.
Confirmed	Nothing	Contact the receiving side, not the sender

The Mistakes That Are Not Delays

Some pending withdrawals are not slow. They are already wrong, and recognising it early changes what you do.

• Missing memo or destination tag. Some networks require a memo, tag or note alongside the address, and the funds land in the receiving platform’s pooled wallet without being attributed to you. The transaction confirms normally, so the chain looks fine. Recovery depends entirely on the receiving platform and is not guaranteed. Contact them with the TXID immediately rather than waiting.
• Wrong network for the right address. An address that looks valid on two chains can be selected with the wrong network chosen at withdrawal. Whether this is recoverable depends on whether anyone controls that address on the destination chain.
• Address copied incorrectly. Clipboard-hijacking malware substitutes a similar-looking address at the moment you paste. If the address in your withdrawal history is not the one you meant to use, the transaction is not delayed — it is gone, and the account should be treated as compromised.

The habit that prevents all three: after pasting an address, compare the first four and last four characters against the source, and send a small test amount first for any destination you have not used before.

When Is It Time to Open a Ticket?

Support is the right move in fewer cases than people assume, and knowing which ones gets you a faster answer.

• Open a ticket if there is no TXID and more than a few hours have passed with no announced maintenance or suspension.
• Open a ticket if the withdrawal shows as completed on the exchange but no TXID was ever produced.
• Open a ticket with the destination — not the sender — if the explorer shows confirmations and the funds have not been credited.
• Do not open a ticket if the explorer shows your transaction unconfirmed. Nobody on the support side can do anything about it, and the queue you join makes things slower for the people who do need help.

When you do write, lead with the TXID, the network, the exact amount, the destination address and the timestamp. A ticket containing those five things gets resolved in one reply; a ticket saying “my withdrawal is pending” gets a request for those five things and costs you a day.

How to Make the Next One Not Do This

• Whitelist your regular addresses. Most exchanges let you pre-approve destinations, and whitelisted withdrawals typically skip the review that catches first-time addresses.
• Do not change security settings on the day you plan to withdraw. The post-change hold is a feature, and it will catch you.
• Match the network to the destination before choosing the asset. Check what the receiving platform expects, then pick that network at the sending end.
• Keep withdrawals under your daily allowance, or split them across days deliberately rather than discovering the cap mid-transfer.
• Keep less on the exchange. The most reliable fix for a withdrawal problem is not needing to make a large, unusual withdrawal under time pressure in the first place.

FAQ

Can an exchange cancel a pending withdrawal?
Only before broadcast. If no TXID exists, cancellation is sometimes possible from the withdrawal history or by support request. Once a TXID exists the transaction is irreversible and no one can recall it.

How long is too long?
With no TXID and no announced maintenance, a few hours is reasonable and a full day is worth a ticket. With a TXID, judge by the explorer rather than the clock — an unconfirmed transaction on a congested network can legitimately take hours.

Does paying a higher fee help?
Not on an exchange withdrawal. The exchange sets the fee and you cannot replace or accelerate its transaction.

The explorer says confirmed but my wallet is empty. Where is it?
Check you are looking at the right network in your wallet, since many wallets show one chain at a time and a token on an unexpected network is invisible until you switch. If the address is right and the network is right, the issue is with the receiving service.

Is a pending withdrawal a sign the exchange is insolvent?
Usually not — individual delays are routine. The signal worth taking seriously is a platform-wide suspension that is not explained, or one whose stated reason keeps changing.

Sources

• Bitget Support — Withdrawal Service Update (September 24, 2026), for the phased resumption example cited above.
• Block explorers referenced for verification: mempool.space (Bitcoin), etherscan.io (Ethereum), tronscan.org (Tron), solscan.io (Solana).

Written September 27, 2026. Specific hold periods, confirmation thresholds and daily limits vary by platform and change without notice — treat the causes above as a diagnostic order rather than as quoted policy, and confirm details against your own exchange’s documentation. This article is informational and is not financial advice.