The short answer
Real USDT is issued by exactly one contract per network. If the transfer in your wallet references that contract and it is confirmed, you are looking at USDT. If it references any other contract, you are not — no matter what the ticker says or how the balance renders.
That single check catches most flash. It does not catch all of it: high-quality flash is built specifically to survive it, which is why the checks below run in order and the last one is time.
Check 1 — the contract address (30 seconds)
Open the transaction on the explorer for its network, not on the wallet app:
- TRC20 — Tronscan
- ERC20 — Etherscan
- BEP20 — BscScan
Find the token contract field and compare it to the official address for that chain:
| Network | Official USDT contract |
|---|---|
| ERC20 (Ethereum) | 0xdAC17F958D2ee523a2206206994597C13D831ec7 |
| BEP20 (BNB Chain) | 0x55d398326f99059fF775485246999027B3197955 |
| TRC20 (TRON) | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t |
A different address is the answer. Flash USDT runs on a modified contract built to imitate USDT — same ticker, same decimals, same icon in the wallet — so the address is the one field that does not lie. Stop here if it does not match.
One nuance: a transfer routed through a smart contract or an exchange can show a different sender while still emitting a genuine USDT transfer event. What matters is the contract that emitted the event, not the address that called it.
Check 2 — the receipt status
A transaction either succeeded or it reverted. On the explorer this is the status field: Success versus Failed or Reverted. A failed transaction costs gas and moves nothing.
Low-quality flash often fails here in a subtler way: the transaction sits pending for hours, or shows as successful while the transfer event is malformed. If the explorer disagrees with your wallet, believe the explorer.
Check 3 — confirmations
Confirmations are how many blocks have been mined since the transaction was included. The threshold that matters depends on what you are doing with the money:
- Releasing goods to a stranger — wait for a meaningful number: 12+ on Ethereum, 15+ on BNB Chain, 19+ on TRON. The detector uses these as its defaults.
- Small, low-risk amounts — three confirmations is usually enough to know the transaction exists.
- Anything you would litigate over — no number of confirmations substitutes for check 5.
Check 4 — can you actually move it?
Send a small fraction of the balance to a second wallet you control. This is the check that separates a display state from a spendable balance.
If the send fails, hangs, or the balance drops to zero without a matching transaction, you are looking at flash. A stuck balance — one that will not move and never recovers — is the usual end state once the injection window closes.
Do not send it back to the person who sent it to you. Send it to yourself, from a wallet you already control.
Check 5 — time
This is the only reliable test against HQ flash. A flash balance holds for 3 to 40 days depending on the network and the configuration used to generate it, then reconciles away or becomes stuck.
If the transfer is material, the honest procedure is: accept nothing, release nothing, and re-check the balance in 72 hours and again at seven days. A balance that survives a week of re-queries is very likely settled. A balance that vanished was never yours.
What each result means
| What you see | Most likely explanation | What to do |
|---|---|---|
| Different token contract | Flash USDT, low or mid quality | Do not release anything. Report the sender. |
| Official contract, transaction failed | Nothing was transferred | Treat as unpaid. |
| Official contract, still pending | Not mined, or a stuck nonce | Wait; do not release on a pending hash. |
| Official contract, confirmed, will not move | Flash with a good contract, window closing | Treat as a display state. |
| Official contract, confirmed, moves, survives a week | Real USDT | Normal settlement risk only. |
Why high-quality flash passes four of these five checks
HQ flash is designed around exactly this checklist. It uses a high-quality contract that renders correctly in major wallets, a V-Hash injector that produces a transaction reading as confirmed, and a lifespan long enough that a merchant who waits an hour — or a day — still sees a healthy balance.
At that quality, checks 1 to 3 pass cleanly and check 4 often passes too, because the balance is movable inside the window. Only check 5 separates it from real USDT.
This is why the detector on this site returns "No Flash USDT detected" for a transaction that used the official contract, with a note that HQ flash can pass. A tool that claims otherwise is selling certainty it does not have.
If you run a business that accepts USDT
Individual checks are not a policy. These five rules are:
- Never release on a screenshot. A transaction ID is not proof either — a real hash can reference a flash contract. Check the contract yourself.
-
Re-query the contract, do not trust a cached
balance. Read
balanceOffrom the official USDT contract at the latest block. A wallet that caches a balance will show you what it was told, not what is true. - Batch your settlements. Paying out on a delay is the single most effective defence: flash balances are built to survive minutes, not weeks.
- Treat exchange deposits as the last line. A centralised exchange runs its own contract checks and review queue, which is why flash deposits are normally caught there rather than credited.
- Log the contract address with every payment. When a dispute arrives three weeks later, the contract is the evidence.
If you already accepted the transfer
Once goods have shipped or funds have left your wallet, the money is gone — there is no chargeback on a confirmed on-chain transfer. Document the transaction, the contract address, the conversation and the wallet, then report it to the platform you met the person on.
Ignore anyone who contacts you offering to reverse it for a fee. That is the second stage of the same scam, aimed at the same person.
Frequently asked questions
How do I know if my USDT is real or flash?+
Open the transaction on the block explorer for its network and check the token contract. Real USDT is issued by one contract per chain: 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum, 0x55d398326f99059fF775485246999027B3197955 on BNB Chain, and TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON. If the transfer references a different contract, it is not USDT.
Can flash USDT show as confirmed on the blockchain?+
Yes. High-quality flash USDT uses a contract built to mirror the real one and an injector that produces a transaction which reads as confirmed. Confirmations alone do not prove a transfer is settled value.
How long does it take to be sure a USDT transfer is real?+
For low-quality flash, seconds: the contract check catches it. For high-quality flash, days: the balance holds between 3 and 40 days depending on configuration, then disappears or becomes stuck. If the amount matters, wait before releasing goods or funds.
Why can't I move or send the USDT in my wallet?+
A balance that will not move is a display state rather than settled value. This is the most common end state of flash USDT once the injection window closes, and it is usually permanent.
Is there a free tool to check a USDT transaction?+
Yes. The Flash USDT Detector on this site reads a transaction ID on TRC20, ERC20 or BEP20, compares the contract against the official USDT contract for that network, counts the confirmations, and returns a verdict.
Open Generator V4, flash a known amount, and check how it renders.