Key takeaways
No TXID: contact the source exchange.
Confirmed on-chain: check destination requirements.
No TXID
Check review status and notices; contact the source if overdueTXID exists, transaction pending
Monitor the correct explorer and do not resendChain succeeded, balance missing
Check confirmations, minimum, and Memo/Tag; contact destinationNo TXID
The withdrawal may still be under review, risk control, or in queue. Check notices and open an official ticket after the stated timeframe.
TXID available
Use the correct block explorer to check status, destination, and amount. If enough confirmations pass without crediting, contact the destination.
Use the TXID to identify the current stage
A missing credit does not automatically mean the funds are lost. Open the source withdrawal detail first. Without a TXID, the request is usually still under exchange review, risk control, or queuing. With a TXID, it has generally been broadcast and can be checked on the matching block explorer.
Do not confuse an order ID, deposit address, and TXID. A TXID may be labeled TxHash or transaction hash and identifies a public on-chain transaction. An internal order ID can only be queried by the platform.
Stage one: no TXID
Check the exact status message, announcements, security notices, and any verification or cooling period. Record time, asset, network, amount, and withdrawal order ID. Without a TXID, a block explorer cannot locate the transfer; contact the source platform rather than the destination.
Do not repeatedly cancel, resubmit, or split orders to bypass review; this can add risk controls or duplicate actions. After the stated timeframe, submit the record through the official app or website.
Stage two: TXID exists but the chain is incomplete
Use the explorer for the correct network, then read status, confirmations, destination, token, and amount. Pending usually means waiting for inclusion. If failed, ask the source when accounting will restore the balance because chain failure and platform bookkeeping are separate.
Do not trust strangers offering to accelerate or unlock the transaction for an advance payment. A recipient generally cannot alter an exchange withdrawal by paying a recovery fee.
Stage three: confirmed but not credited
Verify the destination address, supported asset and network, required confirmations, deposit minimum, and Memo/Tag. On-chain success proves arrival at the address, not that a centralized platform has completed internal crediting.
Contact the destination with the TXID, asset, network, amount, address, time, and screenshots. For a wrong network or Memo/Tag, ask about the official recovery policy and do not send a second verification transfer.
Support evidence and privacy boundaries
You may provide a TXID, public address, order ID, and transaction screenshots. Redact unrelated balances and identity details when the platform permits. Passwords, private keys, seed phrases, one-time codes, and remote device access are never normal troubleshooting evidence.
Enter support only from the official website or app. Search ads, direct messages, and group-chat accounts are not proof of identity even when names and avatars look familiar.
FAQ
Will support ask for a seed phrase?
Legitimate support does not need your seed phrase or private key. Treat any request as high risk.
When should I contact the destination after chain success?
Wait for the destination required confirmations and normal crediting window. If it still has not arrived, contact the destination with the full TXID and deposit details.
Should a delayed withdrawal be reported to authorities?
Troubleshoot an ordinary delay by stage. If fraud, account theft, or an unauthorized transfer is confirmed, secure the accounts, preserve evidence, and contact the platform and relevant local authorities.
Can I send another withdrawal while the first is pending?
Not advisable. Sending a second transfer before the first is diagnosed mixes the records and makes both troubleshooting and any appeal harder. If the problem is the address or the network, the second transfer repeats the same mistake.
Sources and verification
Sources prioritize protocol, network, and exchange documentation. External pages can change; signed-in confirmation screens remain authoritative for fees and account status.