· USDT blacklist · TRON mainnet

TRON scam wallet checker

Screen a TRON wallet before you pay: official USDT blacklist status plus the on-chain behaviour that separates a working business receiver from a throwaway scam wallet.

Two questions, answered in one screen

Paste the wallet and you get a USDT blacklist answer and a behaviour sketch: whether isBlackListed returns true on Tether’s contract, plus its TRX and USDT TRC20 balance and how long the account has existed on mainnet. The contract answers whether the issuer froze USDT for this address. The chain data answers whether this wallet behaves like a running business or a one-shot collector. Neither alone is a full safety verdict, and together they still cannot tell you who is typing on the other end. Use both to decide how much verification the payment deserves before you release funds you cannot claw back.

How a collection wallet usually behaves

Scam receivers share a shape once you have seen enough of them. The account is young, often days old, and funded by a small TRX transfer just large enough to cover the resources a transfer needs. Inbound value arrives from unrelated addresses that never receive anything back — a funnel, not a relationship. Outbound movement is fast and one-directional, sweeping to an exchange deposit or a consolidation wallet within minutes of arrival. Legitimate merchants, brokers and payroll wallets look different: they refund, they pay suppliers, they hold working balances across weeks, and their counterparties recur. Look for two-way relationships over time, not a single impressive number.

Balance and age are weak signals on their own

An empty wallet is not proof of fraud — plenty of honest people sweep every payment to cold storage the moment it lands. A rich wallet is not proof of legitimacy either, because consolidation addresses accumulate exactly the way successful operations do. Age is the least gameable of the three, since an attacker cannot fake history, only buy or reuse an old address. Read them together and in context: a two-day-old wallet requesting an urgent USDT transfer from a person you met last week is a very different object from a two-year-old wallet printed on an invoice from a company you have paid before.

The categories this desk tracks

Entries are grouped so the label tells you something actionable. Phishing covers receivers reported after cloned sites and fake claim pages. Fake support covers helpdesk impersonation, the fastest-growing script in wallet communities. Drainer covers wallets fed by approvals or account permission changes rather than intended payments. Scam OTC covers Telegram and P2P deals where the goods or the counter-payment never arrived. Mixer adjacent is deliberately softer: it records proximity to obfuscation infrastructure, which is a diligence trigger rather than an accusation. Severity separates entries where the loss pattern is well documented from those resting on thinner evidence, so you can weigh a hit sensibly.

When a wallet needs more than a list check

Escalate when three things line up: the counterparty is new, the channel is a messaging app, and the amount would hurt to lose. In that situation a clear result carries almost no information, because the operation had no reason to be reported yet. Ask for a payment route with recourse, insist on escrow you selected, or split the transfer and verify receipt of the first part through a channel you control. Where a deeper picture would genuinely change the decision, the optional deep scan follows exposure across several hops and adds entity labels for that address after one wallet confirmation — network fee only, nothing custodial.

FAQ

The wallet has thousands of transactions. Does volume mean it is trustworthy?

No. High-volume addresses include exchange deposit wallets, OTC desks and laundering consolidation points. Volume tells you the address is in active use; it says nothing about whether the person quoting it to you controls it.

Should I refuse any brand-new wallet?

Not automatically — new wallets are created every day for honest reasons. Treat age as a reason to add friction: smaller first transfer, verification through a second channel, and no urgency-driven exceptions to your own rules.