Where an airdrop reward is actually recorded
You land on a page promising free tokens for connecting a wallet or completing a few tasks, and it shows a reward balance or a countdown clock. That balance exists only on the page. An ERC-20 or TRC-20 token keeps a single balance per address, and a transfer adds to that one number. If tokens had really been sent to you, your wallet's own balance would already include them and the explorer would list the transfer.
On a public explorer, every transfer is its own entry: sender, recipient, the token's contract, the amount and the time it happened. Tronscan shows this for TRON addresses and transactions, and Etherscan shows the same fields for Ethereum. If an airdrop page tells you that tokens have been credited to you, that claim is checkable: either an entry exists naming your address as the recipient, or it doesn't.
Why the contract address decides what you actually received
Tether publishes exactly one contract for USDT on each network: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token that calls itself USDT from any other contract is not Tether's USDT, whatever ticker or logo the claim page shows. An airdrop that promises a stablecoin reward can issue a token with the same name from a different contract. The page's design will not tell you which one you're getting; the contract address will.
Testing an airdrop claim: the contract, then the transfer record
Before you connect a wallet or act on a claim, run two checks that use only public blockchain data. The first two steps below check the contract; the third checks the transfer record.
- Find the contract address the airdrop page names for the reward token. It is often shown next to the claim button. If it only appears inside a transaction the page asks you to approve, read it on your wallet's approval screen and then reject the request without signing.
- Compare that address, character by character, against the official one if the reward is claimed to be USDT: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON, 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum.
- Search your own wallet address on Tronscan or Etherscan and look for a transfer entry listing that contract, your address as the recipient, an amount and a time.
A made-up example: a contract address with one character changed
Picture a claim page telling you a batch of USDT is waiting in your wallet. The page lists a contract address that reads almost the same as Tether's published one, with a single character swapped near the middle. Paste that address into Tronscan or Etherscan and the explorer shows whether it is the contract Tether published or an unrelated one that also uses the ticker USDT. An address one character off is a different contract.
What to do once you've checked
If the contract address matches the one the issuer published, and the explorer shows a transfer entry naming your address as recipient with an amount and a time, the tokens in that transaction are real. That tells you about the tokens only. It does not make the claim page safe, so any request from the page to connect your wallet or sign a transaction still needs its own scrutiny. If the contract doesn't match, or no such entry exists in your address's history, the balance on the claim page is a number on a website with no transfer behind it.
If the result is unclear, for example because you can't be sure the long address matches, TrustSniffer has two free checks. Paste the claim page's address into our website checker to see our report on that site, or a wallet address into our wallet checker to see its on-chain risk report. If either one flags a problem, or you still can't confirm the contract, don't connect your wallet and don't sign anything the page asks for.


