TLoJwAy8aEbQfLEU35txd8nF2ZUtYBBWYN

Case overview

This Tron address came to attention because Tether added it to the USDT blacklist on Tron. The issuer freeze event is recorded on-chain on 2026-09-03, when the wallet held 2,337,660 USDT. The latest scan classifies the wallet as CRITICAL, based on a direct issuer blacklist match.

No verified label, sanctions match, or entity attribution is available for this address. The available evidence shows a young wallet funded by one unlabeled counterparty, holding one asset, then frozen by the issuer. This page walks through the freeze event, possible reasons, and the main caveats.

The freeze event

Tether operates a blacklist mechanism for its USDT token. When an address is added to that list, the issuer typically restricts the address's ability to move or use the affected USDT. For this wallet, TronGrid records an AddedBlackList event on 2026-09-03 at 13:44:21 UTC.

At the time of the freeze event, the observed balance was 2,337,660 USDT. The scan later confirmed the same amount, which is consistent with the funds remaining in the wallet after the blacklist action. The relevant token is Tether USD on Tron, and the contract address is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t.

Because the event type is AddedBlackList, this is not an inferred risk. It is an issuer-level action on the exact address.

Why this wallet may have been frozen

Tether does not publish a public explanation for every blacklist action, so the precise reason is unknown. The evidence supports only a general conclusion: an issuer blacklist match triggers a freeze of USDT at the address. In practice, issuer blacklists are used to stop funds from being moved after the issuer determines the address is connected to prohibited or high-risk activity. That is a possibility here, but it is not confirmed.

A few secondary patterns add context. The wallet was first funded roughly 20 days before the freeze. All tracked USDT came from a single counterparty. Many transfers used round amounts, and most occurred in the same three-hour UTC window. These are low-severity observations and do not by themselves prove wrongdoing. The scan also notes that outside the flagged exposure, the analyzed activity does not indicate broader suspicious behavior.

Funds, counterparties, and labels

The on-chain transfer history shows one incoming counterparty for USDT: TUFgazMpvTxZvq4gd3jRYPww2XTegUNmV1. That address sent 13 USDT transfers to this wallet, totaling 2,337,660 USDT between 2026-08-14 and 2026-09-03. The counterparty has no label, category, or jurisdiction in the supplied evidence. It does not appear as sanctioned or blacklisted in the current dataset.

This single-source structure means the wallet's funds are easy to trace at the address level. It also means the freeze event affects the entire observed balance, not a subset of assets. No verified source-of-funds explanation can be built beyond the on-chain flow itself.

Limitations and caveats

Blockchain evidence is partial. Tether's internal decision-making, including the specific reason for adding this address to the blacklist, is not visible on-chain. A freeze can be lifted or reversed, so the current status should be rechecked before making operational decisions. The transfer analysis is limited to tracked TRC20 USDT activity; it does not capture every native TRX transfer or every historical token movement. Finally, this page is intelligence, not legal advice. It describes what the evidence shows, not what the wallet owner did or whether any law was broken.