On-chain evidence

Quick answer: On-chain evidence is the public transaction trail that can support a scam report. It is valuable, but it must be paired with off-chain context such as chats, emails, websites and payment instructions.

Useful on-chain evidence can include transaction hashes, sending and receiving addresses, contract addresses, token IDs, approval transactions, bridge routes, chain names and timestamps.

Because public addresses are pseudonymous, a transaction hash usually proves that an on-chain event happened. It does not automatically prove who controlled the receiving wallet or whether a named person is responsible.

Good evidence makes it easier to report abuse to exchanges, analytics platforms, wallet vendors, law enforcement and scam databases. Missing details can make an otherwise serious report hard to act on.

Evidence should be saved early. Scam websites, Telegram accounts, Discord servers and fake support chats can disappear quickly after a victim asks questions.

• Funds moved to a new address shortly after a suspicious signature or approval.
• A token approval was granted before assets disappeared.
• The receiving address is linked to other public reports or known abuse databases.
• The scammer instructs you to send funds across multiple chains or through a bridge.
• A recovery contact claims to have found funds but refuses to provide transaction hashes.

1. Create a clean incident folder with screenshots, exports and plain-text notes.
2. Save explorer links and raw hashes, not only screenshots.
3. Record the chain, token, amount, date and wallet label for each transaction.
4. Add website URLs, redirect chains, social handles and support chat IDs.
5. Use evidence to file reports; do not publish private personal details unnecessarily.

• Assuming a wallet address alone identifies a human being.
• Saving only screenshots without hashes or URLs that can be checked later.
• Mixing transactions from multiple chains without labels.
• Paying someone who claims they can reverse a transaction because they “see it on-chain.”

• Chainabuse
• Token approval
• Wallet drainer
• How to report a crypto scam

This page is based on public reporting-tool documentation and wallet-permission references. It is for evidence organization, not attribution of real-world identity.

On-chain evidence is public blockchain data such as transaction hashes, addresses, token approvals and timestamps. It helps document a crypto incident but does not prove identity by itself.

CryptoRescue treats this explainer as a reader-safety page, not as a promotion or a recovery promise. The practical value is in the definition, common risks, verification steps and safer next actions. If a claim cannot be tied to a source, the page should describe it as a signal or reported pattern instead of a settled fact.

• Compare the wording on this page with the original source or official record.
• Save the exact URL, domain, support handle, wallet address or transaction hash if the topic relates to a possible loss.
• Do not pay a separate unlock, tax, AML, validator, liquidity or recovery fee without independent official confirmation.
• Use the warning checker and transaction lookup when the page mentions a service, wallet, domain or payment trail.

On-chain evidence should be read as a source-led safety reference. It does not prove that recovery is possible, that a wallet owner has been identified, or that a service is safe because one warning list has no match. Crypto cases can change quickly, so readers should check timestamps, official domains and the latest linked source before making decisions.

If this page connects to a suspected incident, build a short timeline: first contact, website, payment request, transaction hash, support route and current account state. Then use the CryptoRescue evidence kit, official report portals and exchange or wallet-provider support channels where appropriate.