TRX address TXTZraiS…wM8ef8
TXTZraiS9o9ktwy8j5YEi5WkeXRPwM8ef8
PublicAML knows this Tron address as a darknet address. Our AML risk score for it is 100 of 100, which we read as critical risk. This address is itself listed by documented incident (TXTZraiS…wM8ef8).
What we know about this address
| Chain | Tron (TRX) |
| Category | darknet |
| AML score | 100 / 100 (critical) |
Risk findings
Each row carries the source that flagged it. A row at zero hops names this address directly; any other row is a path our propagation engine traced from a flagged address to this one. A finding is an observation about the flow of funds or about a published listing, not a statement about the owner of this address.
| Finding | Source | Hops | Direction |
|---|---|---|---|
| This address is itself listed by documented incident (TXTZraiS…wM8ef8). | documented incident | 0 | inbound |
| Funds reaching this address are 1 hop from documented incident (TXSon96Y…4FXcaC).TXSon96Yy5gdyniYz16g9QaLabK54FXcaC | documented incident | 1 | inbound |
| Funds reaching this address are 4 hops from OFAC SDN list (TMdZfVVA…QHH3kz).TMdZfVVAsxKsbXGmV3kBnEgM69z3QHH3kz | OFAC SDN list | 4 | inbound |
| Funds reaching this address are 2 hops from documented incident (TAvuMjD6…1sRdHY).TAvuMjD6NShVAFBrViNebrAmKhmH1sRdHY | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (TCi1kGsj…r8AAdR).TCi1kGsj43pP8to56UMLJm6HKuher8AAdR | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (THCqnSpe…yz78CD).THCqnSpeKJBNLm5MxGrhbqU4ZEeTyz78CD | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (TJEvH5aQ…mXTMuF).TJEvH5aQTdnt13iidmnDhqbASGJfmXTMuF | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (TRpopg8r…gwSxeD).TRpopg8rnEULk19vis6ryGFAHFamgwSxeD | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (TNiSqr7D…HbmjBH).TNiSqr7Dc171ct8xScW7RzoBZdXtHbmjBH | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (TTBHx8cc…jU1g87).TTBHx8ccBwnZ7R3qeTTLfRsi2zTkjU1g87 | documented incident | 2 | inbound |
Incidents that name this address
Each line states the role this address plays in the incident as recorded. Being named as a victim, or as the recipient of funds, is not an accusation.
- Named as a perpetrator in xinbi-guarantee-counterparties-2026-09. Source: publicaml.org
More addresses in this index
These are other addresses in the PublicAML directory, not counterparties of this one. Nothing here implies a connection between them.
If this page is wrong
Attribution and risk propagation both make mistakes, and a page like this one is visible for a long time. If you own this address or can show that a finding here is incorrect, tell us and we will re-check it. Corrections are applied to the underlying data, so they carry over to the API and to every other view of this address.
See something wrong on this page? Tell us and we will check it.
PublicAML reports what it can observe on-chain and what public and vendor sources say about an address. Nothing on this page is a legal finding, an allegation against a person, or advice. Risk scores describe exposure through transaction paths, and an address can carry exposure without its owner having done anything wrong.
Data is read live from the PublicAML API at the time this page was served.
Is this your address?
Leave your email and we will watch this address for you: you hear from us when money moves through it or when what we know about it changes. We cannot recover anyone’s money, and we will not pretend otherwise — but you will not have to keep checking.
We use the address only to reach you about this wallet. No password to choose: you sign in with a code we email you.
If you want to put the whole account on record — what happened, when, how much — file a report. We never publish who filed one.