OFAC-sanctioned Tron addresses

OFAC publishes digital-currency addresses as a field on SDN entries, the same way it publishes a passport number or a vessel IMO. As of 2026-07-24 the SDN list carries 195 Tron (TRX) addresses, belonging to 25 designated persons. All of them are below.

Why an address list is not a screening control

OFAC adds and removes addresses without notice, and a designated person can move funds to a fresh address at any time. There are three specific ways a static copy of this table fails in production:

• It goes stale. The SDN list is republished on OFAC's schedule, not yours. The list this page was built from was published 2026-07-24.
• It is chain-scoped. This page covers Tron. A product that settles on several chains needs all 963 addresses across every chain OFAC publishes, not one chain's worth.
• It only catches exact addresses. The same designated persons are also blocked by name, and most sanctions exposure arrives as a counterparty name rather than an address already on the list.

Who these Tron addresses belong to

All 195 Tron addresses on the SDN list

Reproduced exactly as OFAC publishes them, newest designation first. The owner column is the primary name on the SDN entry the address is attached to.

Programs these addresses were designated under

Screen this programmatically

The same data behind this page is available as a single unauthenticated GET. It checks an address against every digital-currency address on the SDN list, and returns a match list rather than a yes/no so you can log what matched and why:

curl "https://sanctionsai.dev/sanctions?wallet=TPyE2oSoaysrXfLzwf9wetBVr9JudLwjtD"

The free tier allows 5 checks per day with no signup, which is enough to wire the call up and see the response shape. Production limits and the audit log are on the paid tiers; the API reference covers batch screening and the degraded flag you should alert on.