Separate three questions: what the chain records, what can be inferred, and what another party knows. A strong privacy claim must define all three.
What an explorer can show
Scroll horizontally to read all columns.
| Field | What it establishes | What it does not establish alone |
|---|---|---|
| Transaction identifier and block | A particular recorded transaction and its inclusion. | The legal identity of a participant. |
| Token contract, amount and events | Which token operation was recorded. | The commercial purpose or legitimacy of the payment. |
| From, To and token recipient | Addresses involved in the operation. | That every address belongs to a separate person. |
| Timestamp and account history | Timing and observable activity. | A conclusive explanation of intent. |
Attribution needs additional evidence
A service may associate a deposit address with a customer account. A published invoice or screenshot may reveal another connection. Those are examples of information outside the raw transaction that can affect attribution.
An address label in an explorer can be useful but should not be treated as a court finding. Distinguish the recorded chain event from a label, an inference or a claim about who controls an account.
What a privacy mechanism would need to prove
A mechanism can seek to make a particular linkage harder under defined assumptions. To evaluate that statement, you need the deployed system, the adversary model, the evidence available to that observer and the known limitations.
A claim that a service “breaks the chain” is too broad without those definitions. It does not follow that all records are erased, that every observer lacks a link or that future attribution is impossible. StableScope does not provide instructions for hiding unlawful proceeds or bypassing controls.
Privacy, custody and issuer control are independent
A service could make a narrow privacy claim while taking full custody of your assets. A self-custody tool could still expose public transfers. Neither situation resolves the issuer’s ability to restrict the token.
Circle and Tether publish terms describing issuer restrictions. A change of address, asset route or interface does not itself remove the conditions attached to the token or bind a receiving platform’s decisions.
Reduce unnecessary disclosure without moving funds
These are data-handling precautions, not promises of anonymity. They do not change the onchain record or your legal obligations.
- Avoid posting wallet balances, deposit screens and support tickets publicly.
- Redact personal information from screenshots before sharing them.
- Use verified support channels and disclose only what is needed to resolve the issue.
- Keep seed phrases and private keys offline and out of any support conversation.
- Do not assume a public transaction hash is harmless when it connects your identity with an address.
Timing, amount and address reuse add context
Scroll horizontally to read all columns.
| Pattern | What it can contribute | What it cannot prove alone |
|---|---|---|
| Timing correlation | A close sequence of deposits and payouts can be a clue for an analyst. | A complete identity or a unique causal link. |
| Amount correlation | Similar amounts can narrow a hypothesis when combined with other evidence. | That two transfers came from the same person. |
| Address reuse | Reusing an address can connect otherwise separate public activity. | That a fresh address has no offchain association. |
| Split payouts | Several outputs can still be compared by timing, amounts and counterparties. | That a service erased the source or destination history. |
These are analytical boundaries, not instructions for hiding unlawful proceeds. A privacy mechanism must state its observer model and evidence limits; “breaks the chain” is not a sufficient specification.
Source-of-funds questions sit outside the explorer
A receiving platform may ask how funds were obtained or why a transfer was made. A new address, a different token or a split payout does not answer that question or remove the platform’s review obligations.
Keep invoices, transaction identifiers and other records privately where they are lawful and necessary. Do not publish sensitive account data to prove a point, and do not treat a privacy-labelled service as a substitute for a legitimate records process.
Sources & review
Editorial review: Sep 21, 2026. Source-specific dates and retrieval limits are stated where relevant. Issuer and service statements are attributed, not independently audited; a citation is not an endorsement.
- Ethereum · Block explorers (opens in a new tab)
Public transaction, token and account fields.
- Circle · USDC terms (opens in a new tab)
Redemption eligibility, blocked addresses and issuer rights.
- Tether · Legal terms (opens in a new tab)
Issuer terms and restrictions; check the applicable entity and document.