Your exchange marks the BTC withdrawal as completed. The destination address shows nothing. This gap has a defined set of causes and a defined troubleshooting sequence. The exchange marking a withdrawal as completed means it has left the exchange's custody — not that the transaction has been confirmed on the Bitcoin blockchain, and not that the destination address or network was correct. These are three distinct events, and the gap can exist at any one of them. Bitok Arena Research has mapped the sequence that resolves most cases without needing to contact anyone.
The exchange's withdrawal status screen is not a blockchain record. It is the exchange's internal record of what it instructed its wallet software to do. The transaction exists on the Bitcoin blockchain only after it has been mined into a block. These events are related but not simultaneous — and not always both true when the exchange shows "completed." The block explorer is the source of truth, not the exchange dashboard.
When an exchange shows a withdrawal completed but the destination address shows nothing, start with the transaction hash. The exchange provides a transaction ID (TXID) when a withdrawal processes — it appears in the withdrawal history, sometimes labeled "transaction hash" or "TxID." Paste that string into a Bitcoin block explorer: Mempool.space, Blockstream.info, or Blockchain.com/explorer. If the transaction appears with one or more confirmations, it is on the blockchain. If it appears with zero confirmations, it is in the mempool awaiting confirmation. If it does not appear at all, the exchange has not yet broadcast it to the Bitcoin network despite showing "completed" internally — this lag occurs on some exchanges and typically resolves within minutes to an hour.
Confirmation Count and the Destination
Many on-chain Bitcoin applications require a minimum number of network confirmations before reflecting an inbound transaction. A transaction at zero confirmations (in the mempool) or one or two confirmations is real and on its way — it is simply not yet at the required threshold. Bitcoin blocks confirm approximately every ten minutes under normal conditions, so a transaction that entered the mempool with an adequate fee should reach three confirmations within 30–45 minutes. If the mempool is congested and the transaction fee was set too low, the wait may be longer. Check the current mempool fee environment on Mempool.space to understand where the transaction sits in the queue before concluding something is wrong.
Bitok Arena compiled the troubleshooting sequence for BTC withdrawal not appearing at an on-chain destination, ordered by frequency of cause.
Get the TXID — find the transaction hash in the exchange withdrawal history; this string links the exchange record to the blockchain record.
Check the block explorer — paste the TXID into Mempool.space; if the transaction appears, note the confirmation count; if not, the exchange has not yet broadcast it.
Verify confirmation count — 0 confirmations: waiting in mempool; 1–2: approaching the required threshold; 3+: destination application should reflect the entry within minutes.
Verify the destination address — in the transaction Outputs section, confirm the receiving address matches the intended destination; a mismatch means the BTC went to a different address.
Most non-appearance situations resolve at step three — confirmed but recent, with the destination updating shortly after.
An address rejected by the exchange when attempting withdrawal indicates an address format compatibility issue. Native SegWit addresses beginning with bc1q are rejected by some older exchange withdrawal interfaces that display an error stating the address format is invalid. This is an exchange interface limitation, not an issue with the destination address itself. The workaround: withdraw from the exchange to a personal wallet that the exchange accepts — Legacy (1xxx) or P2SH (3xxx) format — and then send from that personal wallet to the bc1q destination. Any valid Bitcoin address format produces a valid on-chain transaction received by Native SegWit addresses.
Wrong Network and Wrong Address
The most serious scenario — BTC confirmed by the exchange but absent from any Bitcoin block explorer — occurs when the exchange processed the withdrawal on the wrong network. Some exchanges present BTC withdrawal options that include BEP-20 (Binance Smart Chain), ERC-20 (Ethereum), or other non-Bitcoin networks. A BTC withdrawal processed over BEP-20 produces a token on the Binance Smart Chain, not a Bitcoin mainnet transaction. It will not appear on any Bitcoin blockchain explorer. If the exchange shows the withdrawal completed but no TXID appears on Bitcoin blockchain explorers, a cross-chain network selection error is the probable cause.
Bitok Arena identified three categories of withdrawal failure by their block explorer symptoms and recovery options.
Wrong network (BEP-20, ERC-20) — transaction will not appear on Bitcoin blockchain explorers; the TXID may appear on the Binance Smart Chain or Ethereum chain instead; recovery depends on whether the destination address is also valid on that non-Bitcoin chain.
Wrong Bitcoin address — transaction appears on Bitcoin blockchain going to an unintended address; cannot be reversed; not recoverable without cooperation from whoever controls that address.
Correct network, correct address, insufficient confirmations — transaction appears going to the correct destination; waiting for the required confirmation threshold resolves the non-appearance.
Prevention: verify the network selection explicitly before confirming withdrawal; verify the first and last six characters of the destination address against the application display.
Why an exchange withdrawal from a shared address creates a position problem is worth understanding before sending. When an exchange processes a withdrawal, the BTC leaves an exchange-controlled address that may be shared among thousands of users — not the user's personal address. Any application reading who sent the BTC to a destination address will see the exchange's shared address, not the individual user's address. This is why the path for any destination that reads the sender's address is always: exchange → personal self-custody wallet → destination. Once the exchange-to-personal-wallet transaction is confirmed, the BTC is under the user's control and the subsequent send comes from their specific address.
After the Transaction Confirms
A withdrawal stuck at the exchange level — where even the TXID is not yet available — means the exchange's processing queue has not released the transaction. Most exchanges process withdrawals within 10 to 60 minutes. If a withdrawal remains in "pending" status beyond two hours, the exchange's support team can investigate using the withdrawal reference number from the withdrawal history. The resolution at this stage is entirely with the exchange — the Bitcoin network has not yet seen the transaction, so there is nothing to track on a block explorer until the exchange broadcasts it.
The exchange says it sent. The block explorer says it confirmed. The destination application shows the receipt. These three statements should all be true before the situation is resolved. When they are not, the reason is in one of four places: broadcast not yet happened, confirmations not yet at threshold, wrong network selected, or wrong address received the funds. Check in that order.
The transaction hash from every exchange withdrawal is the evidence trail that resolves any troubleshooting question without needing to contact anyone. Save it at the time of withdrawal. Paste it into Mempool.space immediately after the exchange shows "completed" — if the transaction appears with a confirmation count and the output addresses include the correct destination, the only remaining variable is time. If it does not appear, the exchange has not yet broadcast it. If it appears going to an unintended address, the input error happened at the withdrawal confirmation step. The block explorer does not interpret or explain — it shows what the blockchain recorded. That record is the only authoritative source for what actually happened to the BTC after the exchange processed it.
Bitok Arena's analysis of BTC withdrawal troubleshooting identifies four causes across every non-appearance scenario: broadcast delay, insufficient confirmations, wrong network, and wrong destination address. The block explorer resolves which applies within seconds of pasting the TXID — no support ticket needed for three of the four; only wrong-network errors require exchange investigation.