A free AML check is a lookup on Tronscan or Etherscan

Before a transfer goes either way, you want to know whether the address on the other end is safe to deal with. The free check is a lookup on a public blockchain explorer: Tronscan for TRON addresses, Etherscan for Ethereum. Search the address or a transaction hash and every transfer shows its sender, recipient, token contract, amount and time. Reading those fields yourself is an AML (anti-money laundering) check: it asks whether the address is linked to funds or activity you would not want to touch.

A token keeps one balanceOf number per address

An ERC-20 token like USDT on Ethereum keeps one balance per address, tracked by a single function called balanceOf. A transfer adds to the recipient's existing balance, so the amount that just arrived becomes part of the same number as the tokens the address already held. TRON's TRC-20 standard works the same way.

The number on an explorer or in a wallet app does not show which contract issued the token. The transfer history does, because every transfer lists its contract, and that field settles whether a token calling itself USDT is real. Genuine USDT has exactly one contract per network, TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token that calls itself USDT from any other contract is not Tether's USDT.

Two wallets that look the same until you check the contract

Picture two wallets that each show a USDT balance right after a deposit arrives. Both are made up for illustration.

Nothing about the number on screen tells the two apart. Only the contract field on Tronscan or Etherscan does.

  • Wallet A received its deposit from the TRON contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, the one Tether actually controls. Its balance is backed by real USDT.
  • Wallet B received a transfer labelled USDT from a different contract address entirely. Its balance looks identical in a wallet app, but the tokens behind it are not Tether's.

A genuine token and a trustworthy sender are two different checks

Confirming the contract address tells you the token is genuine. It does not tell you whether the sender is trustworthy, or whether the address has a history connected to other flagged activity. Tronscan and Etherscan show the full list of counterparties an address has transacted with, each entry carrying its own contract and time stamp, and an AML read is built from that list. TrustSniffer's wallet checker reads the same history and returns a risk read on the address, so you do not have to work through every transfer by hand. Treat a flag from it the way you would treat a bad sign you found yourself: hold off on any transfer to or from the address until you know why. If a website told you to expect the deposit or asked you to send funds, check the site as well. The website checker looks at the site itself.

Reading an address yourself before you run a dedicated checker

You do not need an account to do the first part of this yourself. Four things to look at, in order:

A match on the contract address confirms the token is genuine. If the sender, recipient or time does not fit what you were told about the transfer, stop before you act. If you are still unsure after reading the history, run the address through a dedicated checker, which answers the same question faster than reading every transfer by hand.

  • Open Tronscan or Etherscan and search the wallet address or the transaction hash you are checking.
  • Read the token contract field on the transfer. The name displayed next to it does not confirm anything.
  • Compare that contract address character by character against Tether's own contracts: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON or 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum.
  • Look at the sender, recipient and time fields together and see whether the transfer matches the story you were told about it.

Frequently asked questions

Is a free AML check the same as a compliance check an exchange runs?

This article covers the check you can run yourself on a public explorer. We have no evidence on what any particular exchange or compliance team runs internally, so we do not describe it here.

Does a matching contract address prove a wallet is not involved in a scam?

It proves the balance shown is backed by the issuer's real token. Whether the address is otherwise connected to reported scams is a separate question, which is what a risk checker built on top of the explorer data is for.

What if my wallet app shows a different balance than the explorer?

Both read the balanceOf figure from a token contract. If the numbers differ, check that the app shows the same address and the same token contract as the explorer. A single mistyped or swapped character in a saved address points to a completely different wallet, and a token labelled USDT from another contract has a balance of its own that is not Tether's.