What Matters
A crypto transfer marked completed by the sender is not, by itself, proof that the receiving exchange has credited your account. Trace the exact transaction on the correct network, check its execution result and destination, then compare the evidence with the receiver’s requirements. Use the worksheet below to identify the next question before repeating the transfer or opening a support case.
DN Evidence Block
Last verified: 26 October 2026. Scope: five official help pages from Coinbase, Kraken and Binance. Original DN contribution: a transfer-state decision table, evidence worksheet, synthetic worked case and support-request template.
Decisive finding: sender status, on-chain execution, receiving-account credit and withdrawal availability are different evidence checkpoints. Kraken’s documentation even distinguishes some deposits usable for trading from those available for withdrawal. [1]
Method: documentation review, not funded-account testing. DN did not trace reader accounts, submit recovery requests or measure support performance. The 2027 guide uses evidence reviewed in October 2026. Current account instructions take precedence over this general workflow.
Start by identifying the transfer you actually made
Record whether this was an on-chain transfer, an internal exchange transfer, a bridge route, or a payment sent to an email address or phone number. They do not share one tracing method. An internal book transfer may have an account reference instead of a public blockchain transaction. A bridge can involve a source transaction and a separate destination transaction.
This guide focuses on a direct on-chain transfer into a custodial exchange account. For a self-custody destination, there is no exchange crediting queue to investigate; you instead need the correct wallet account, network and asset display. For a bridge, trace each leg through the route provider’s official documentation before interpreting a source-chain success as destination receipt.
Keep the sending account’s withdrawal reference separate from the blockchain transaction ID. Kraken describes the transaction hash as a way to inspect addresses, confirmations and timing, and provides it within funding transaction details. [2]
DN Transfer-State Decision Table
Use the first row that matches your evidence. The contact listed is a sensible starting point, not a guarantee of responsibility, recovery or response time.
| Observed state | What it establishes | Next check / starting contact |
|---|---|---|
| Sender says completed; no verifiable chain record | The sender has labelled its own record. Public broadcast is not established by that label alone. | Confirm transfer type and exact network; ask the sender for the blockchain hash or internal reference. |
| Explorer says pending / unconfirmed | The intended chain transaction has not yet reached the required confirmed state. | Inspect sender guidance and network conditions. A receiving exchange cannot manufacture confirmations. |
| Explorer says failed | The intended execution did not succeed. | Ask the sender to reconcile its account entry. Do not assume the receiver can credit a failed transfer. |
| Explorer says dropped / replaced | The hash you are viewing may no longer be the relevant transaction. | Ask the sender for the replacement hash; trace that record instead. |
| Successful execution; destination or asset route does not match | Successful execution is not proof of compatibility with the intended exchange account. | Use the receiver’s official missing-deposit or recovery process. Eligibility is case-specific. |
| Successful matching transfer; below receiver’s confirmation requirement | The transaction may be on-chain while still awaiting exchange eligibility. | Check the exact asset/network requirement and current maintenance notices. |
| Successful matching transfer; requirements appear met; no credit | You have evidence suitable for a receiving-side investigation. | Check account alerts, deposit history and official status pages; contact receiving support with the evidence pack. |
| Balance credited; trading or withdrawal unavailable | The problem has moved from receipt to availability. | Check that product’s status and account restrictions; use the balance and withdrawal-hold guides. |
Binance’s official tracing guide separately discusses failed transactions, replacement hashes and successful execution. Its Tron example also distinguishes confirmation from the transaction’s success or failure result. [3] Do not reduce every explorer screen to one green confirmation badge.
Read the chain record before diagnosing an exchange problem
Open the explorer link from the transaction’s official account record where available. Confirm that the explorer is for the network actually used. A familiar-looking address or matching ticker does not establish the correct chain or token representation.
Inspect the intended asset movement and receiving address, not just the top-level transaction summary. Token transactions can include several entries; the question is whether the relevant transfer reached the intended destination with the expected asset and amount. Save the hash and a timestamped observation. A screenshot is useful context, but a verifiable transaction reference is better evidence than a cropped status badge.
If you cannot find a hash, do not immediately conclude that funds were stolen or never sent. First resolve whether the transfer was internal, the reference was copied incorrectly, the network is wrong, or the sender has a separate broadcast record. Ask the sender to clarify the discrepancy.
Then compare the receiver’s exact requirements
Record the supported asset and network, assigned deposit address, any required memo or tag, deposit minimum, confirmation policy and current service status. Use the instructions for your account and jurisdiction. Do not assume that another exchange’s thresholds apply.
Kraken’s processing-time guidance says its deposit crediting depends on network confirmations, points users to its status page for maintenance, and cautions that network conditions affect timing. [4] A published estimate is not an account-specific delivery promise. This guide deliberately does not turn one asset’s current confirmation count into a universal waiting period.
Coinbase’s troubleshooting guidance tells users to verify the destination address and network, inspect the transaction link, and review account alerts for outstanding information requirements. [5] If a task appears necessary, complete it through the authenticated app or official website. Do not follow unsolicited recovery instructions from a social-media reply.
DN Transfer Trace Worksheet
Copy this register into your own notes. Mark each item verified, mismatch or unknown. An unknown remains an open question; it is not a passing check. This is a manual worksheet and sends no information to DN.
| Checkpoint | Evidence to record privately | Status / observation time |
|---|---|---|
| Transfer type and sender | On-chain / internal / bridge; sending reference; initiation time and timezone | ________ |
| Chain evidence | Network; hash; explorer URL; execution result; observed confirmations | ________ |
| Destination match | Actual receiving address versus assigned address; memo/tag match if required | ________ |
| Asset and quantity | Asset identifier / contract where relevant; actual amount sent or received; fee treatment | ________ |
| Receiving conditions | Supported route; minimum; required confirmations; instructions captured with timestamp | ________ |
| Account and service state | Deposit-history entry; account alert; official incident or maintenance notice | ________ |
| Next action | Unresolved question; official support case ID; stated next-update time if supplied | ________ |
Decision rule: no chain evidence → clarify with sender; failed or replaced record → resolve the sender-side record; successful compatible transfer without account credit → prepare a receiving-side case; credited but unusable → investigate availability. Multiple mismatches can coexist.
Worked example: a completed withdrawal is not yet a credited deposit
Synthetic illustration, not a real exchange incident. At 10:00 UTC, a user requests a transfer of 500 units of TOKEN. The sender’s receipt states that a 1 TOKEN withdrawal charge is deducted, leaving an expected transfer of 499 TOKEN. At 10:03, the sender shows completed. At 10:06, the correct explorer shows successful execution to the assigned address, with 499 TOKEN transferred and eight observed confirmations.
In this fictional case, the receiving instructions require twelve confirmations. The user records the four-confirmation shortfall, checks for an incident notice and keeps watching the existing transaction. DN does not translate that shortfall into minutes: block timing and receiver processing are not fixed.
Later, the same record shows fifteen confirmations, but the deposit history still has no credit. The user now submits the hash, address match, amount, network and captured receiving instructions to the receiver. This evidence narrows the investigation; it does not prove that a particular support outcome or recovery is guaranteed.
The amount check is 500 − 1 = 499 TOKEN. Another platform might charge the fee separately. Always read the actual receipt rather than assuming this deduction model. There is no reason in this example to resend 500 TOKEN merely because the first deposit is not visible.
A support request that asks an answerable question
Use the authenticated support channel for the relevant platform. Keep one coherent case history and add new evidence to it where possible. Only include account identifiers inside that private channel. Public hashes and addresses can still expose transaction history, so avoid posting a complete financial trail publicly.
Copyable support template
Transfer type: [direct on-chain / other, explain]
Asset and network: [exact identifiers]
Sender reference and blockchain hash: [both, labelled separately]
Official explorer link: [URL]
Amount actually transferred and fee treatment: [quantity]
Initiated / observed times, including timezone: [times]
Execution result and current confirmations: [evidence]
Receiving address and memo/tag match: [verified / mismatch / unknown]
Receiving requirements checked: [minimum, confirmations, supported route]
Deposit-history status and relevant account alert: [details]
Official service notice, if any: [URL and observation time]
Please confirm whether this transfer has been detected, which requirement remains outstanding, and whether I should use a specific missing-deposit process. Please provide the case reference and next step.
For a failed or missing sender-side record, change the subject and request accordingly: ask for broadcast evidence, the replacement hash or reconciliation of the withdrawal entry. Never send a seed phrase, private key, password or one-time authentication code as part of a trace.
What not to infer from a delay
A delay alone does not establish insolvency, theft, permanent loss or that a second transfer will repair the first. A successful chain transaction also does not guarantee recovery when the chosen asset, network, address or memo is incompatible. Avoid anyone promising guaranteed recovery in return for an advance payment or wallet access.
Do not send extra funds to clear an unexplained deposit, attempt a blind bridge, or sign an unfamiliar transaction to unlock a custodial credit. An exchange support case ordinarily concerns its own ledger and processing rules. A wallet signature is a different action that needs its own clear purpose.
After receipt: verify availability before moving on
Save the final deposit entry and reconcile the amount. Check separately whether the balance can trade and whether it can be withdrawn. Kraken’s documented statuses illustrate why these are distinct; its intermediate credited state is not used for every asset. [1]
Continue with DN’s Balance Reconciliation Guide or Withdrawal Holds Guide when the funds have arrived but the displayed or available balance still needs explanation.
Before your next transfer
Use the DN Deposit Checklist for prevention. If you are comparing a future venue, start with DN Pathfinder and check the Venue Switching Cost Calculator. A new account does not resolve an existing missing deposit, and an advertised network list is not a substitute for current account deposit instructions.
Commercial disclosure: linked DN tools or reviews may contain affiliate links. These are optional research pathways, not recovery services. No exchange signup is required to use this tracing worksheet.
Methodology, limits and corrections
DN compared five public support documents and organized their distinctions into a general troubleshooting sequence. The worksheet and worked case are DN editorial tools; they are not a funded benchmark, venue reliability score or diagnosis of your account. We do not rank these providers or claim that any is fastest. Support rules, account entities and supported assets can change. Edition 1.0, 26 October 2026: initial publication package. Report outdated guidance through DN’s contact page with the source URL; never send credentials.
Frequently Asked Questions
Does completed mean the receiving exchange credited my account?
Not by itself. Check whose status you are reading, then verify the chain record and the receiver’s deposit history and requirements.
Should I send the same transfer again?
Do not repeat it merely to clear an unexplained delay. Trace the existing record and establish the next action first; another transfer can create another unresolved deposit.
Who should I contact first?
Start with the sender for missing broadcast evidence, failed execution or a replacement hash. For a successful matching transfer that meets receiving conditions but remains uncredited, start with the receiver’s official support process.
Is a confirmed transaction always successful?
No. Read the execution result as well as the confirmation state. Binance’s official guide includes a Tron example where a confirmed transaction has a failed result.
Can a missing deposit always be recovered?
No. Recovery eligibility depends on the asset, route, destination and provider’s rules. This checklist makes the evidence clearer; it does not guarantee recovery.
Primary sources
- Kraken: Cryptocurrency deposit statuses — page updated 5 May 2026.
- Kraken: Finding a blockchain transaction ID — page updated 2 April 2025.
- Binance: Checking transaction status on-chain — page updated 19 December 2025.
- Kraken: Cryptocurrency deposit processing times — page updated 22 October 2026.
- Coinbase: Send and receive troubleshooting — reviewed 26 October 2026.
All sources reviewed 26 October 2026. General operational education; not individualized investment advice or a recovery service.
