Table of Contents
A wallet can show a USDT balance and still fail every send, receive, and issuer redemption if Tether has listed that address on the official USD₮ contract for that chain.
Check blacklist status by calling isBlackListed(address) (capital L) on Tether's official contract for the named chain. On Ethereum the same view is also exposed as getBlackListStatus. false means clear as of that query. true means transfers involving that address revert, and redemption fails because redemption requires a transfer.
This guide is the operator checklist for Tether's blacklist. For Circle USDC's parallel call, see how to check if a USDC address is blacklisted. For why issuers freeze at all, see can stablecoins be frozen.


Key Takeaways
- Call Tether's isBlackListed on the official USDT contract for the settlement chain.
- Spelling differs from Circle: Tether uses capital L (isBlackListed); USDC uses isBlacklisted.
- true blocks send and receive; the balance can still display; issuer redemption fails too.
- Blacklist state is per contract and per chain; Ethereum clear does not mean Tron clear.
- A false result is a snapshot, not a permanent clearance.
What isBlackListed actually answers
Tether's USD₮ contracts include a blacklist path. When an address is listed, the contract refuses USDT movement for it even though other chain traffic still settles.
The view you want is isBlackListed(address). On Ethereum official USDT it is also available as getBlackListStatus. Both return a boolean for one address on one USDT contract. They do not screen OFAC lists, exchange policies, or a different chain's USDT.
Named downside: a false result is a snapshot. Tether can list the address later. A clear on-chain address can still be venue-locked. Querying the wrong-chain contract gives a useless boolean.
Before you query: name the chain and the official contract
Blacklist state is per contract. The same 0x string clear on Ethereum is not a Tron clearance.
Copy the official USDT address from Tether's supported protocols page for the chain you are settling on. Confirm character-for-character with how to check the official USDC or USDT contract.

| Chain | Official USDT to query | Explorer read path |
|---|---|---|
| Ethereum | 0xdAC17F958D2ee523a2206206994597C13D831ec7 | Etherscan Read Contract → isBlackListed / getBlackListStatus |
| Tron | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t | Tronscan Read Contract → isBlackListed |
Do not paste Ethereum's contract onto Tron, and do not trust a ticker clone labeled USDT.
How to run the Ethereum check (Etherscan)
Open Etherscan's official USDT token page. Confirm the contract is 0xdAC17F958D2ee523a2206206994597C13D831ec7.
Open Contract → Read Contract. Find isBlackListed (Tether spelling: capital L). You can also use getBlackListStatus. Paste the counterparty wallet address and Query.
Record true / false, the contract address, the chain, the block or timestamp, and who ran the check. For automated rails, call the same view from your node or indexer immediately before you build transfer / transferFrom.
How to run the Tron check (Tronscan)
Open Tronscan's official USDT TRC-20 contract. Confirm TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, open Read Contract, find isBlackListed, paste the Tron address, and query.
Over half of frozen USDT sat on Tron in Stablecoin Insider's August 2026 freeze guide figures. If your corridor is Tron-heavy, make the Tronscan check mandatory, not optional.
| Result | What it means for settlement | What to do next |
|---|---|---|
false | Address is not on Tether's USDT blacklist for that contract now | Proceed under existing receive controls; re-check before large tickets |
true | USDT send/receive involving that address will revert | Stop settlement; do not treat the visible balance as movable dollars |
| Wrong contract / chain | Boolean is about a different token instance | Restart from Tether's supported-protocols list |
| Explorer / RPC error | No trustworthy answer | Fail closed; do not settle on a failed read |
What true blocks (and what it does not)
When isBlackListed is true, Tether's path reverts transfers that touch the listed address. The wallet can still display a USDT balance. Display is not spendability.
Issuer redemption also needs a transferable balance. A blacklisted address cannot complete the transfer redemption requires, so redemption fails too. Tether can also call destroyBlackFunds on listed balances.
A venue holding your USDT in its own omnibus wallet is a different failure mode. The exchange can lock your account while the on-chain check on your deposit address still returns false. Run both checks when the product path mixes self-custody and exchange balances.
Scale context (why operators screen)
From Stablecoin Insider's freeze guide (figures as published August 2026): Tether had frozen $4.2B+ across 7,200+ addresses; Circle roughly $109M across about 372. Only about 3.6% of blacklisted addresses had ever been removed.
A February 2026 Istanbul-linked action froze $544M. In one 30-day window ending May 2026, Tether blacklisted 384 addresses totaling about $515M, mostly on Tron. Tether-stated figures in that guide also cite work with 340+ law-enforcement agencies across 65 countries, 2,300+ cases, and $4.4B+ in assets frozen.
Those numbers explain why treasury desks screen before settlement-sized inbound. Full freeze mechanics live in can stablecoins be frozen.
Spelling trap: Tether vs Circle
Circle USDC uses isBlacklisted. Tether USDT uses isBlackListed (capital L). Searching the wrong casing on the explorer wastes minutes and can look like a missing function.
Do not mix the two booleans. A clear USDC address can still be frozen for USDT on the same 0x string, and the reverse.
Where this fits in send and redeem controls
Treat the blacklist query as a gate after the contract match and before you mark a receivable paid or fire an outbound.
For outbound USDT, confirm the official contract, run isBlackListed on the destination, then follow the same discipline you use when you send USDC to another wallet. For issuer cash-out paths, remember redemption needs a transferable balance; see how to redeem a stablecoin for dollars.


What not to do
Do not trust a ticker, a green check, or a CoinGecko page as a freeze clearance.
Do not query Ethereum USDT and call it a Tron blacklist check.
Do not settle after a failed RPC read. Fail closed.
Do not assume yesterday's false covers today's wire-sized ticket. Re-query.
Do not confuse an exchange lock with Tether's on-chain blacklist.
Next step
Add the Ethereum and Tron queries to your pre-settlement checklist, dual-control the contract string against Tether's supported-protocols list, and re-run the check on every material inbound before you book cash.
FAQ
Where do I call isBlackListed for USDT?
On Tether's official USDT contract for the settlement chain, via the explorer Read Contract UI or your own RPC call. Start from Tether's supported-protocols list, not a search hit.
Does a visible USDT balance mean the address is not blacklisted?
No. Blacklisted addresses can still display a balance. The contract blocks movement; it does not always hide the row.
Is an exchange account freeze the same as isBlackListed?
No. Venues can lock platform balances while the on-chain issuer blacklist for a deposit address remains false. Check both when your flow uses a venue.
Why does Tether use capital L and Circle use lowercase?
That is how each issuer named the view on their contract. Search isBlackListed for USDT and isBlacklisted for USDC so the explorer finds the function.
What if isBlackListed returns true after I already received USDT?
Stop further sends from that address, quarantine the receivable, and escalate through compliance. Removals are rare (~3.6% historically in Stablecoin Insider's freeze data), and redemption will not clear while transfers revert. Tether may also destroy blacklisted funds.
Does a clear Ethereum check cover Tron?
No. Blacklist state is per contract and per chain. Run the Tronscan check on TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t when the corridor is Tron.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.