TBunenmoyeqeqK6jx3wejuu18YyERaVvQC

What the issuer action shows

On July 5, 2026, Tether issued an AddedBlackList transaction on the Tron chain that froze the USDT held in address TBunenmoyeqeqK6jx3wejuu18YyERaVvQC. The on-chain event transferred approximately 4,399,118.715 USDT to the blacklist, rendering those tokens unavailable for further movement.

Most likely freeze drivers

Tether's blacklist is typically applied to addresses linked to illicit activity, sanctions evasion, or violations of its acceptable-use policy. Although the exact trigger for this wallet is not disclosed, the combination of a direct issuer blacklist match, rapid fund movement, and high outbound concentration suggests a compliance-driven freeze rather than a technical error.

Funds and counterparties

The wallet received inbound USDT from a variety of sources. The largest single inbound was 4,400,600 USDT from TThsdRiB3UBbHtn4NFQCcPqNaEMCgYpPSS, with additional inflows from several other addresses. The funding source recorded by the scanner is TBEVZSfGgCbKRmYVARrr411hAk1cUD72gn. Outbound activity shows an extreme concentration: essentially all tracked outbound volume went to one counterparty (TPwezUWpEGmFBENNWJHwXHRG1D2NCEEt5s). This pattern, together with rapid pass-through and fan-in/fan-out flows, raises layering concerns.

Signals for compliance teams

• Extreme outbound concentration to a single address
• Rapid pass‑through of large inbound amounts within an hour
• Fan‑in/fan‑out and circular counterparty flows
• Very young wallet age (~22 days) limiting behavioral history
• High inbound concentration from a few counterparties

Evidence and limits

The freeze is supported by an on-chain AddedBlackList event (tx hash 652fb27e…) and a DIRECT_ISSUER_BLACKLIST_MATCH flagged by the scanner. Inbound and outbound flows are derived from the transfer window covering June 18 – July 7, 2026. However, blockchain evidence is partial; off-chain context or Tether’s internal criteria are not visible. The observed balances may change, and the extraordinary outbound value could reflect a data anomaly. No sanctions matches, labels, or Iranian source appear in the supplied data, so any such attribution remains unconfirmed.