Skip to content
← Tools & guides

Transfer not received: check execution, asset movement and credit separately

Documentation-based guide · Updated

Follow an existing transaction from its network and hash to the actual recipient. Separate a successful contract call from a payment and a platform credit.

Before you start

  • Have the full transaction hash, sending network, expected recipient and native asset or token contract. An internal order ID is not an onchain hash.
  • The onsite checker supports Ethereum, BSC and Base. For other chains, use that network’s explorer. This workflow reads an existing record; no wallet connection or signature is needed.

1. Match the network and full hash

Copy the hash and network from the original sending record. Select that network in the transaction checker and compare the returned hash. The same 0x address format is used on several chains; it does not identify the chain.

If the transaction is not found, check for an incomplete hash, an order ID or the wrong network. A single node’s missing record cannot establish that a transaction failed or was never broadcast.

Check: Save the network, full hash, explorer URL and observation time. If identity is unresolved, record ‘not located’.

2. Read the execution state

A pending response has no execution receipt yet. A reverted receipt means that execution failed; gas can still be charged. Preserve the visible error instead of guessing its cause.

A successful receipt is the start of the asset check. Confirmation counts are observations of additional blocks, not a universal finality guarantee. Use the receiving service’s current requirements; Base and Ethereum have different settlement models.

Check: Classify the result as not located, pending, failed or successful. Do not label it credited yet.

3. Identify what moved and to whom

For a direct native-asset transfer, compare sender, recipient and value. For ERC-20 tokens, compare the full token contract, Transfer recipients and amounts. A contract call’s top-level To field can be a token or router rather than the final recipient.

The onsite tool shows at most five decoded ERC-20-style transfers from the first 30 receipt logs; metadata is read for at most three token contracts. It does not trace internal native-asset movements, NFTs or every nonstandard token. Open the explorer for those cases. A missing row in this limited view is not proof of no movement.

Check: Match chain, asset contract, actual recipient and amount. Mark an unsupported movement as unresolved.

4. Check receiving-service credit separately

If the recipient is a platform account, compare its current supported network, asset, deposit address and any applicable credit conditions with the matched onchain movement. This page does not know that platform’s private account ledger.

For a cross-chain operation, the source-chain receipt is only one stage. Locate the original protocol’s message or destination record before concluding that the destination received anything. Preserve missing evidence; do not send another transfer as a diagnostic test.

Check: Record onchain movement and platform credit as separate findings. Save the service’s receipt or identify the missing requirement.

Worked example: a successful approval is not a payment

  • Illustrative ERC-20 case, not a transaction executed by this site: the decoded input is approve(spender, 1000000), the receipt succeeds, and the log is Approval.
  • The allowance is a raw integer. Token decimals have not been verified. There is no matching Transfer to the expected recipient in the supplied evidence.

Conclusion: The supplied record supports a successful approval call. It does not establish a payment or platform credit, and 1000000 cannot be described as one token without knowing the decimals.

Decision & failure branches

Observed evidence, its limits and the next check
ObservationWhat it meansNext check
Not foundThis node has no matching transaction or receipt on the selected network.Recheck network and hash; compare with the sender’s existing broadcast record and explorer.
PendingThe queried node sees the transaction but has no receipt.Save the pending state and time. Waiting does not guarantee inclusion.
Failed / revertedExecution failed; gas may still have been spent.Preserve the error and original record. Do not infer successful asset delivery.
Success, movement not matchedA successful call alone does not prove the expected payment.Inspect function, logs and explorer traces; distinguish approval from transfer.
Movement matched, platform credit missingOnchain delivery and private platform credit are different states.Check current platform conditions and provide the existing evidence to its official support.

Completion checklist

  • Keep the full network, hash, asset identity, recipient, amount and check time.
  • State execution, asset movement and platform credit independently; keep unresolved stages explicit.

Official sources