USDT transfers on public networks create visible transaction records. Explorers can show addresses, amounts, token contracts, timestamps, and transaction hashes. A mixer claim should be read against that visibility, not as a replacement for it.
What it means
This page anchors the entire cluster because most mixer claims depend on how readers understand public-chain records. If visibility is misunderstood, every later claim about privacy, risk, or review criteria becomes weaker.
What it does not prove
Explorer visibility does not always identify a real-world person. It also does not prove that an analytics label is complete. It shows the public transaction layer that must be interpreted with additional context.
Network context
ERC20 records are reviewed with Ethereum tooling, while TRC20 records are reviewed with Tron tooling. The visible fields are conceptually similar, but the ecosystems, fees, and labeling coverage differ.
Evaluation checklist
- Name the visible transaction fields.
- Separate on-chain facts from off-chain records.
- Explain address history without overstating identity.
- Link visibility claims to explorer context.
Source notes
These sources are used for terminology, risk framing, or primary-source context. They do not verify private service claims.
Related questions
Are USDT transactions public?
On public networks, token transfers are visible through compatible block explorers.
Does visibility equal identity?
No. Visibility shows transaction data. Identity usually requires exchange records, platform records, or other off-chain evidence.
Why does this matter for mixer pages?
A mixer page that ignores public-chain visibility leaves readers with an incomplete privacy picture.