How to check a crypto transaction: pending, confirmed or not credited
Use the transaction hash and correct network to work out whether a crypto transfer is pending, failed or confirmed but missing from your account.
In this guide · 9 sections
- Find the transaction on the correct network
- Read the status before taking another action
- Count confirmations without confusing them with credit
- Check what moved, not just whether execution succeeded
- When a confirmed transfer is not credited
- Understand what fees can and cannot change
- Prepare the details for official support
- Questions about checking a crypto transaction
- What the sources establish
Find the next check for your crypto transfer
Choose the status you observed to find the relevant next check. This guide does not inspect a transaction, connect to your account or determine whether funds can be recovered.
No personal details are needed. Do not share recovery words, passwords or banking credentials.
Browse all situations and next checks
- I am not sure what the status means
- Start with the sending record
- Open the sending wallet or provider yourself and find the asset, network and transfer record.
- Distinguish an internal order or withdrawal reference from a transaction hash before searching an explorer.
- Use the guide to identify which stage you can actually verify.
- The provider shows a withdrawal, but I have no transaction hash
- Clarify whether the withdrawal was broadcast
- Ask the sending provider whether this is still an internal request or an onchain transaction.
- Request the network and transaction hash if it says the transfer was broadcast.
- Do not treat an internal reference as evidence that the network accepted the transfer.
- The correct explorer shows pending or unconfirmed
- Read the network status before retrying
- Check that the hash and network match the sending record.
- Read the wallet or provider documentation for the particular pending status; fee changes are not available for every transfer.
- Avoid a second payment merely to make the first one appear.
- The explorer shows failed or reverted
- Read the failure and fee information separately
- Distinguish the attempted transfer or contract action from the network fee.
- A failed contract call is not the same as a successful payment to the recipient.
- Read the relevant network and wallet explanation before trying another action.
- The explorer shows success, but my account has no credit
- Separate network confirmation from account credit
- Compare the destination, asset, network and any required memo with the receiving instructions.
- Check the receiving service’s published confirmation requirements and account status.
- If the transfer details match but credit is still absent, give official receiving support the transaction evidence.
- I found a different network or a missing memo
- Move to the network and memo guide
- Keep the exact transaction record and the receiving instructions together.
- Identify who controls the receiving address before assuming a wallet setting can solve the issue.
- Use the separate guide to prepare questions for that wallet or receiving provider.
To check a crypto transaction, copy its transaction hash from the sending wallet or exchange, open an explorer for the network actually used, and inspect the status and recipient. If the transaction is confirmed but not credited, compare the transfer with the receiving platform’s deposit instructions. Blockchain confirmation and an account balance update are different events, which is why Coinbase’s troubleshooting instructions ask users to check both the network and destination.
A useful diagnosis ends with a specific finding: no broadcast evidence, awaiting inclusion, failed execution, a destination mismatch, or a transfer that needs the receiving provider’s attention. It should also tell you what evidence supports that finding. A green badge by itself cannot answer all those questions, and refreshing the balance screen cannot fix every kind of delay.
This guide was substantially rewritten on October 21, 2026. It explains how to inspect the records yourself, with hypothetical examples rather than claims of tested deposits. Canadian readers should first distinguish a crypto transfer from Canadian dollar funding: if the missing payment was an Interac e Transfer into a cash balance, use our Interac crypto deposit troubleshooting guide for Canada. There may be no blockchain transaction to find for that bank payment.
Find the transaction on the correct network
The correct starting point is the sending record for the particular transfer, including its network and transaction hash. Open the withdrawal or transaction details from inside the application you used. Copy the complete hash using its copy control, if available. Record the asset and network exactly as displayed, without shortening a network name to the name of the coin. Keep the account’s withdrawal reference separately; it can help support even when it cannot be searched on a blockchain.
Before opening an explorer, describe the journey in one sentence. For example: “I withdrew an asset from an exchange to my own wallet,” or “I sent a token from my wallet to a deposit address.” That small exercise identifies which side created the transfer and which side should display it. If the sentence instead describes a purchase, a card charge or money moved between balances inside an application, start with that provider’s record before assuming a public blockchain payment occurred.
Obtain the hash from the actual sending record
A hash identifies a particular transaction, whereas an address identifies a destination or account on a network. An exchange may also give you an internal withdrawal ID. Those fields can look similarly technical, so use their labels rather than judging by appearance. Ethereum’s transaction documentation distinguishes the transaction’s sender, recipient, value and nonce, the sequence number associated with the sending account. These describe different parts of the transaction, not interchangeable search references.
If another person sent the funds, ask for the network and transaction hash in text. A cropped screenshot saying “completed” is a starting point, not enough to inspect the transfer. Ask them to reopen the transaction details in their sending application. You do not need their login, recovery phrase or access to their device. If they cannot supply a hash, record that fact without immediately deciding that the payment is fraudulent; they may be looking at the wrong reference or a request still awaiting processing.
If your own exchange shows a withdrawal request but no hash, check its status wording and any explanation in that same screen. The unresolved question is whether the provider has broadcast a transaction. Ask its official support to confirm the network, broadcast status and current hash. Trying arbitrary strings in several explorers adds noise to the investigation. The withdrawal reference is the better evidence for the sending provider until there is an identifiable transaction on the network.
Choose the explorer from a trusted network reference
Use the explorer link in the sending application or one identified in the network’s official documentation. Check the site address and the network name before pasting the hash. Searching a hash is a read operation: it should not require importing a wallet, signing a message or granting token access. Keep the task limited to inspecting public details. An advertisement or chat message offering a wallet “synchronisation” service is not necessary to look up a transaction.
A token name alone does not identify the network that carried it. Treat the sending network as an independent field, alongside the asset and destination. If the sending record and receiving instructions name different networks, save both records and move to our wrong network and missing memo guide. Waiting for more confirmations will not change the network recorded in a transaction. Avoid trying a second transfer until you understand which network the recipient accepts.
Where an application offers several explorer links, use the one associated with the actual transfer stage. A bridge journey can involve a sending side and a receiving side, with different references. Label those stages in your notes instead of assuming that one successful page proves the whole journey completed. For a bridge issue, the useful question is which stage remains incomplete according to that bridge’s official interface. Do not apply a plain exchange deposit checklist as though it establishes a bridge’s settlement status.
What “transaction not found” actually tells you
An empty search result tells you that this explorer did not return the transaction you requested. It does not, by itself, prove that no transaction was ever created. First paste the hash again directly from the source and confirm the network. Then check whether the sender has issued a replacement hash or whether the record you copied is an internal reference. Record the explorer’s result and the time you checked so the absence has a useful context.
When the hash and network are correct but the result is still missing, compare another established explorer for that same network, if one is available through trusted documentation. Treat disagreement as unresolved evidence. Do not average the two answers or select whichever looks reassuring. Give the sending provider both results and ask which transaction it considers current. There is no useful reason to pay a stranger to “activate” a missing explorer entry.
- Sending requestThe wallet or provider records your instruction. An internal request is not proof of broadcast.
- Network recordA matching transaction hash lets you inspect the transfer on the correct network.
- Block inclusionRead the transaction outcome and the network’s confirmation or finality information.
- Account creditThe receiving provider applies its deposit requirements and matches the transfer to an account.
A later stage needs its own evidence. A successful network transaction does not establish that the receiving account has been credited.
Read the status before taking another action
Read status at the transaction level before deciding whether to wait, replace or contact the recipient. Pending inclusion, successful execution, reverted execution and a credited platform balance are different observations. An explorer displays blockchain information; a receiving application displays its own account record. Put the two statuses next to each other in your notes, preserving their exact wording rather than translating everything into “sent.” That makes a later conversation with support much less ambiguous.
| What you can establish | What remains unresolved | Useful next step |
|---|---|---|
| Withdrawal request exists, no hash supplied | Whether a transaction was broadcast | Ask the sending provider for broadcast details |
| Transaction is visible but not included | Whether and when it will enter a block | Check the sender’s supported pending transaction options |
| Transaction is included and execution succeeded | Whether the intended asset reached the intended destination | Inspect recipient, amount and transfer details |
| Ethereum transaction shows reverted execution | Why the call failed and which fee was charged | Read the error and review the sending application |
| Correct transfer meets the recipient’s stated requirements | Why its account ledger has not updated | Send the evidence to receiving support |
Pending does not identify the cause
Treat “pending” as a state that needs more context, not a diagnosis of a low fee. Is the word shown by your exchange, your wallet or the explorer? A provider may be describing its withdrawal workflow while the explorer is describing inclusion in a block. In your notes, write “pending in the sending app, no hash supplied” or “hash visible in explorer, no block recorded.” These statements point to different questions and prevent a generic fee recommendation from being applied to the wrong problem.
For an ordinary Ethereum account, transaction ordering also matters. A later transaction can depend on an earlier nonce being processed. MetaMask’s pending transaction guidance therefore tells users to address the oldest pending transaction first. If several sends are waiting, inspect their order before trying to accelerate only the newest one. Keep each hash with its associated nonce so that you do not confuse a replacement attempt with a separate payment.
Do not make a fresh payment simply because a pending one is inconvenient. Before using any retry control, establish whether it replaces the original transaction or creates another independent send. If the application does not explain that distinction, stop at the inspection stage and consult its official documentation. The relevant concern is duplicate payment: an unresolved first attempt and a newly created second attempt can leave you investigating two transfers instead of one.
A reverted Ethereum call is not a successful deposit
A transaction can be included in a block while the action it attempted fails. For an Ethereum transaction whose execution reverts, the intended transfer within that reverted execution does not take effect, although gas used is paid. The Solidity error handling documentation explains state reversion, and Ethereum’s gas guide explains why execution fees apply to failed transactions. This is different from successfully sending the principal to an unintended address.
Read the error field before deciding what to repeat. Record whether the explorer says reverted, out of gas or another execution error, and retain the full transaction link. A red error on one internal call is also not automatically the same as a failed transaction overall: contract code can handle certain internal failures. Base your first classification on the transaction receipt’s overall status, then ask the application to explain any contract behaviour you cannot interpret from the visible record.
Suppose, hypothetically, a wallet attempted to transfer 40 tokens and the whole execution reverted. The useful investigation separates the intended 40 token payment from the native currency spent on gas. It would be wrong to describe both as a successful deposit, and equally wrong to conclude that all 40 tokens were necessarily lost. Check the token balance, fee and any other transactions around that time. If the sender was an exchange, its account history may require separate reconciliation by that exchange.
Count confirmations without confusing them with credit
A Bitcoin transaction receives its first confirmation when it is included in a block on the active chain. Each subsequent block adds another confirmation. It does not begin at zero after inclusion. Bitcoin.org’s definition of confirmation makes this distinction explicit. The receiving service decides what confirmation requirement it applies to a deposit; the explorer’s number does not select that requirement for it.
For a hypothetical arithmetic check, imagine that a transaction is included at block height 900,000 and the current tip is 900,002. Its confirmation count is three: 900,002 minus 900,000, plus one. The “plus one” counts the inclusion block itself. This example is not an observation of a real transfer. It is a way to spot an off by one mistake when a support explanation and an explorer appear to disagree.
Keep the time of the observation with the count. “Three confirmations at 14:05 UTC” is more useful than “three confirmations” copied into a ticket hours later. The recipient may inspect the transaction after the count has changed. If you update the ticket, give the newer observation without deleting the earlier one. That preserves the sequence and helps distinguish a deposit that had not yet met a requirement from one that continued to be missing after it did.
Bitcoin depth and Ethereum finality answer different questions
Bitcoin’s protection against a transaction being reorganised out of the active chain is probabilistic: additional depth reduces the risk, rather than creating an absolute customer guarantee at a universal count. Ethereum’s proof of stake system has an explicit finality mechanism based on validator votes. Its consensus FAQ distinguishes this economic finality from the probabilistic finality associated with proof of work. Neither mechanism is the same event as a platform updating a customer’s balance.
For practical troubleshooting, write down the actual label provided for the network you used. If the explorer distinguishes inclusion from finalisation, preserve that distinction. Do not translate an Ethereum finality indicator into a Bitcoin style number of minutes, or apply a Bitcoin confirmation threshold to an unrelated network. Ask the receiving service what its own requirement is for this asset on this network, and compare like with like.
A changing count also needs context. If an explorer unexpectedly shows fewer confirmations, save the observation and cross check the same transaction on another suitable explorer. Ask whether the page is current and whether the transaction remains in the active chain. Do not infer a refund from a lower number. Your record should identify what changed, when you saw it and which source displayed it, leaving the cause open until the evidence supports an explanation.
There is no single waiting time for every deposit
Use the receiving platform’s current deposit instructions for the exact asset and network. Record its requirement as a policy you checked on a particular date, not as a rule for all crypto deposits. If it provides an estimated processing period, read what starts that period: a submitted withdrawal, a broadcast transaction or completion of the required confirmations. A time estimate measured from the wrong starting event can make a normal workflow appear overdue.
Consider a hypothetical recipient that says it credits after a stated number of confirmations and a processing step. If the blockchain requirement has been met, the next question concerns that processing step, not how to buy another confirmation. Conversely, if inclusion has not happened, a promise about internal account processing does not resolve the network delay. This distinction lets you ask a narrower question instead of accepting the same generic instruction to wait for every possible problem.
Check what moved, not just whether execution succeeded
The transfer details must match the asset, destination and amount you intended. A success badge tells you that a transaction executed successfully under its rules; it is not a personalised assessment of your payment instructions. Work from the receiving instructions and match them against the explorer. Avoid beginning with the overall value displayed at the top and assuming it represents the amount credited to your account.
Bitcoin outputs can include more than your payment
A Bitcoin transaction can have multiple inputs and outputs. The Bitcoin developer guide explains that outputs allocate amounts that can later be spent. For a deposit investigation, locate the output paying the intended receiving address and read its amount. A transaction’s total output value can include payments to other addresses, so it is not automatically the value of your individual deposit.
Here is a hypothetical reading exercise. A transaction contains outputs of 0.003 BTC, 0.004 BTC and 0.001 BTC. Your deposit address is attached to the 0.003 BTC output. Your evidence should identify that address and amount, not report that 0.008 BTC was sent to your account. You do not need to identify the owners of the other addresses to describe your payment. If an output index is displayed, retaining it can make the relevant output easier for support to locate.
An address page and a transaction page also answer different questions. The transaction page helps establish a particular transfer. The address page may show activity over time. If you are investigating an earlier payment, keep the original transaction as the anchor instead of assuming the address’s present balance must still equal that payment. Ask the receiving provider to reconcile the specific deposit with your account record; do not substitute a snapshot of a later balance for the transfer evidence.
Token activity may be separate from native currency value
On Ethereum, an interaction with a token contract is different from a plain ETH transfer. A transaction’s top level value can describe ETH while token movements appear separately in decoded transfer details. The ERC20 specification defines token transfers and approvals as different operations. A successful approval grants permission under the token’s rules; it is not itself proof that the intended deposit transfer occurred.
Inspect the token transfer entry associated with the intended asset, including the contract and destination. Compare the contract with the receiving platform’s supported asset information where it publishes that detail. A familiar ticker or icon is not enough for this comparison. If you cannot establish that the token is the expected one, record “asset identity unresolved” instead of stating that the platform received the supported asset. That uncertainty matters more than a large confirmation count.
In a hypothetical example, someone expects a stablecoin deposit but opens a successful transaction showing zero ETH value. Zero ETH alone does not answer whether tokens moved. They should inspect the token transfer details and distinguish an approval from a transfer. If those details show no matching transfer, the successful transaction does not establish the expected deposit. If they do show a matching transfer, the next check is the recipient’s acceptance criteria, not another attempt to make the ETH value nonzero.
Read both records together. Neither a screenshot nor a status label alone answers every deposit question.
When a confirmed transfer is not credited
A confirmed transfer becomes a receiving account issue only after you establish what arrived and compare it with the receiving service’s instructions. Check the supported network, asset, deposit address, any required memo or tag, minimum amount and confirmation requirement. Kraken’s missing deposit checklist, updated October 14, 2026 and checked for this guide on October 21, includes these checks and directs users to its maintenance status. It illustrates why confirmation alone cannot settle a missing credit investigation.
Create two columns in a private note: “receiving instruction” and “actual transfer.” Copy the exact network name into each, then do the same for asset, address and memo if applicable. For amount, use the amount delivered in the relevant transfer rather than the amount you originally typed into a sending form. Mark an item “unknown” if the record does not establish it. An incomplete comparison is more honest, and more useful to support, than a list of unchecked assumptions marked correct.
Compare the deposit amount after relevant deductions
If a receiving platform specifies a minimum, compare it with the qualifying amount under that platform’s instructions. Keep any sending fee separate. For example, hypothetically, a sender requests 25 units and the sending record says that a one unit withdrawal fee is deducted, leaving 24 units to be delivered. The original request for 25 does not prove that a 25 unit receiving minimum was met. Verify the actual transfer and the recipient’s policy before concluding which amount counts.
Do not send a top up automatically to repair a below minimum deposit. First ask whether the receiving service combines deposits, requires each transfer to meet the minimum, or offers another process for the existing transfer. Those are provider decisions. The useful question is specific: “Does another transfer affect the treatment of this existing deposit?” Without a clear answer, another send can incur another fee while leaving the first issue unresolved.
Also separate asset quantity from its displayed Canadian dollar value. A portfolio screen may show a changing valuation even when the number of units is unchanged. When investigating whether a deposit arrived, compare units of the same asset first. Then, if necessary, investigate the exchange rate or valuation shown. Mixing a CAD estimate on one screen with a token quantity on another can create an apparent discrepancy that has nothing to do with a missing blockchain payment.
Distinguish a wallet display problem from an exchange ledger problem
For your own wallet, identify the exact account and network being displayed before investigating the balance. Keep the comparison tied to the receiving address from the original transaction. For an exchange deposit, the provider must associate an accepted transfer with your customer account. These are different contexts. An explorer cannot tell you which private customer ledger entry a service created, and a wallet application’s display should not be treated as the provider’s ledger.
Write down where the balance is missing: the asset page, deposit history, available balance or another named screen. If the deposit appears in history but is unavailable, preserve its status and explanation. If it does not appear anywhere, say that instead. Support can investigate those observations more effectively than a broad statement that the funds “disappeared.” Keep screenshots narrow enough to show the issue without exposing unrelated holdings or account information.
If the transfer is correct and the published requirements are met, check the recipient’s official service status and account notices. An incident notice can explain the provider’s stated handling, but do not assume every missing deposit belongs to that incident. Save the relevant notice with the time you checked and ask support whether it applies to your specific network and transfer. If no notice applies, provide your comparison and request an explanation of the unresolved credit.
Understand what fees can and cannot change
Fees can affect network inclusion, but paying more cannot correct an already confirmed recipient, change a token contract or force a platform to credit an account. Before discussing a fee increase, identify the unresolved stage. “My transfer has no block yet” and “my recipient has not credited a confirmed transfer” need different responses. Keep this distinction visible when reading advice online, especially advice that recommends the same paid acceleration service for every symptom.
For Ethereum, the execution fee depends on gas used and the effective price per unit. The gas limit is a cap on computation, not the fee already paid. Ethereum’s fee documentation explains the calculation and the distinction between the base fee and priority fee. For inspection, copy the actual transaction fee shown after execution rather than assuming the maximum amount offered was all spent.
As a hypothetical arithmetic example, 30,000 gas used at an effective price of 12 gwei gives a fee of 360,000 gwei, or 0.00036 ETH. This is a calculation, not a current fee estimate or a recommended setting. Keep the units visible when comparing your own record. A Canadian dollar equivalent adds a price conversion that can vary with its valuation time, so the native currency amount is the cleaner starting point for reconciling the fee.
Pending replacement depends on the wallet and network
Bitcoin replacement by fee concerns replacing an unconfirmed transaction with one spending at least one of the same inputs and paying a higher fee. Bitcoin Optech’s RBF explanation distinguishes node policies, including replacement policies that do not depend on the original opt in signal. It would be misleading to promise that every wallet can accelerate every pending payment, or to treat one explorer’s replaceability badge as a complete description of available options.
Use your sending wallet’s documented controls if you decide to attempt a replacement. First confirm that you control the sending wallet, that the original remains pending, and that you understand the revised payment and fee. If a custodial exchange created the transaction, ask that exchange about its options rather than trying to manipulate its transaction from an unrelated wallet. Save the original and replacement hashes together and check which transaction eventually appears in a block.
Ethereum wallet cancellation similarly involves an attempt to replace a pending transaction rather than recalling a confirmed one. MetaMask’s cancellation instructions explicitly limit the attempt to pending transactions. Do not read an available Cancel button as a completed cancellation. Recheck the resulting status before assuming the payment can no longer occur, and use the wallet’s current instructions instead of copying fee values from an old screenshot.
Record the status at the time you check a fee estimate. If the sender has not supplied a transaction hash, start with the withdrawal request and account checks instead of choosing a higher fee. A provider’s internal review is a different stage from a transaction waiting for inclusion; changing a wallet fee cannot resolve a request that the provider has not established as broadcast. Keep the provider reference, network and observation time together.
Prepare the details for official support
A useful support request identifies the unresolved step and provides enough information to reproduce your comparison. Start from the help area inside the provider’s application or its independently verified website. Do not use a phone number found in an advertisement, an unsolicited direct message or a public reply to your complaint. You are requesting an investigation of a transaction, not granting control of a wallet.
Keep one private record containing the sending provider or wallet, receiving service, asset, exact network, transaction hash, receiving address and amount. Add the memo or tag if relevant, the sending reference and the observation times with time zone. Include the explorer link and the receiving instruction you compared against. These details work together: a hash without a network can leave ambiguity, while a network without a hash may not identify the payment.
Describe the problem in the first sentence of your request. For a hypothetical case: “The transfer is included on the stated network and the receiving address matches my deposit instructions, but my deposit history has no entry.” Follow that with the recorded evidence and the remaining uncertainty. If you have not verified the asset contract or required memo, say so. Do not claim that support has received a qualifying deposit until the comparison establishes it.
Ask for an answer appropriate to the unresolved stage. The sender can clarify whether a withdrawal was broadcast and whether a hash was replaced. The receiving service can explain whether it recognises a transfer, which deposit requirement remains unmet, or what additional evidence it needs. A wallet developer can explain its display or transaction controls. Directing a question to the party that controls that stage avoids a circular conversation in which each side is asked to solve a different system’s problem.
Preserve evidence without making the transaction public
A transaction hash is not a signing secret, but sharing it publicly can expose financial activity associated with the transfer. Bitcoin.org’s privacy guidance explains that public transaction records can reveal balances and activity once an address is linked to an identity. Share the details privately through the official case channel. When asking a general question in a forum, omit account identifiers and transaction details that are unnecessary to explain the symptom.
Never include a recovery phrase, private key, password or authentication code in the evidence package. Review screenshots for unrelated information before attaching them. Keep original copies privately and make separate redacted copies for general discussion if needed. A support request should let someone inspect the public transfer and your provider record; it should not let them spend funds or take over an account.
Maintain a short chronology after the first request. Record when the case was opened, the reference provided, what support asked for and the exact answer you supplied. Add a new explorer observation only when it changes the diagnosis or answers a question. Sending the same screenshot repeatedly can obscure the one meaningful change, such as a transaction entering a block or a provider confirming that it does not support the network used.
If someone demands another crypto payment to release the existing balance, or asks for a recovery phrase to investigate it, pause that interaction. A delayed deposit alone does not establish a scam, but a new demand may change the problem you need to solve. Our guide to responding to a crypto scam in Canada covers preserving evidence and choosing the next reporting step when there are signs of deception.
Questions about checking a crypto transaction
Does one confirmation mean my Bitcoin deposit should appear?
One confirmation means the transaction has been included in a block on the active chain. Whether a service credits it at that point depends on its current deposit requirements and processing. Look up the requirement for the exact asset and network, then compare the transaction details with the deposit instructions. A confirmation is evidence about the blockchain, not a promise about an account balance.
Why does the explorer say success while my balance is unchanged?
First establish that the successful transaction contains the transfer you expected. Check the recipient and asset, not just its top level status. Then distinguish your own wallet display from a receiving platform’s account ledger. If the transfer matches the instructions and the required processing conditions have been met, give the receiving provider the hash and your comparison so it can investigate the missing credit.
Can a block explorer refund or recover my transfer?
An explorer is a way to inspect blockchain records. Looking up a transaction does not give the explorer control of its funds or the receiving service’s account ledger. Bitcoin.org’s practical guidance explains that a Bitcoin payment cannot simply be reversed by a third party. Questions about an accepted transfer or possible return belong with the relevant recipient or provider, without assuming recovery is available.
Should I pay a higher fee when the deposit is already confirmed?
A higher inclusion fee does not repair a confirmed transfer’s destination or make a recipient credit its customer ledger. Inspect the actual transfer and receiving requirements. If those match, investigate the provider’s processing rather than buying acceleration. Fee replacement is relevant only to an eligible pending transaction and depends on the sending wallet and network rules.
Is a failed Ethereum transaction the same as losing the transfer amount?
No. If the whole execution reverted, the intended state changes in that execution did not take effect, while gas used is still charged. Inspect the overall status, fee and asset balance, and distinguish that attempt from any other transaction. If an exchange initiated it, ask that exchange to reconcile its own withdrawal record. Do not infer the fate of the principal from the word “failed” alone.
What if I only have an Interac reference?
Use the bank funding route first. An Interac reference identifies the bank payment record, not a crypto transaction hash. If you later bought crypto and withdrew it, those are separate steps with their own records. Trace the missing step using the Canadian Interac deposit checklist before searching a blockchain for a payment that may never have used one.
What the sources establish
The checks below show which documents support the technical distinctions used in this guide. They were consulted on October 21, 2026. The workflow, numerical examples and evidence organisation are editorial explanations, not measurements of provider performance. No deposit, recovery attempt or support response was tested for this rewrite.
| Question | Primary evidence | Limit of that evidence |
|---|---|---|
| When does Bitcoin confirmation begin? | Bitcoin.org vocabulary | Does not set an exchange’s credit policy |
| How do Bitcoin and Ethereum finality differ? | Ethereum consensus FAQ | Does not promise a universal deposit time |
| What happens when Ethereum execution reverts? | Solidity error handling and Ethereum gas documentation | Does not reconcile a custodial account ledger |
| Is an approval the same as a token transfer? | ERC20 specification | Does not prove that an arbitrary token is authentic or supported |
| Why can a confirmed deposit be missing? | Kraken’s deposit checklist | Describes that provider’s checks, not every provider’s policy |
| Can cancellation reverse a confirmed Ethereum send? | MetaMask pending transaction guidance | Availability depends on wallet, network and transaction state |
Sources and further reading
- Bitcoin.org: Confirmation vocabulary
- Bitcoin developer guide: Transactions
- Bitcoin.org: Things you need to know
- Ethereum: Transactions
- Ethereum: Proof of stake frequently asked questions
- Ethereum: Gas and fees
- Solidity: Error handling and state reversion
- Ethereum Improvement Proposals: ERC20 token standard
- Kraken: Cryptocurrency deposit is missing
- Coinbase: Send and receive troubleshooting
- MetaMask: Speed up or cancel a pending transaction
- Bitcoin Optech: Replace by fee
- Bitcoin.org: Protect your privacy