Dex Router (OKX) — ETH address 0x5B9768…6A78A3
0x5B97684A8D8eF27BDf3E1100dF807A539A6A78A3
PublicAML knows this Ethereum address as Dex Router (OKX), a dex. Its AML score is 0 of 100 because we treat this address as infrastructure (known dex — infrastructure, AML floored). Exposure that reaches it is not scored against it, and the findings below describe what we traced rather than an accusation. Funds reaching this address are 3 hops from OFAC SDN list (0x098b71…3e2f96).
What we know about this address
| Chain | Ethereum (ETH) |
| Entity | Dex Router (OKX) |
| Category | dex |
| AML score | 0 / 100 (floored from 70, treated as infrastructure) |
| Cluster size | 440,294 addresses |
Risk findings
Each row is a path our propagation engine traced from a flagged address to this one, with the number of hops and the source that flagged it. A finding is an observation about the flow of funds, not a statement about the owner of this address.
| Finding | Source | Hops | Direction |
|---|---|---|---|
| Funds reaching this address are 3 hops from OFAC SDN list (0x098b71…3e2f96).0x098b716b8aaf21512996dc57eb0615e2383e2f96 | OFAC SDN list | 3 | inbound |
| Funds reaching this address are 3 hops from OFAC SDN list (0x6fac4d…4ab9c0).0x6fac4d18c912343bf86fa7049364dd4e424ab9c0 | OFAC SDN list | 3 | inbound |
| Funds reaching this address are 4 hops from OFAC SDN list (0xdcbeff…643193).0xdcbeffbecce100cce9e4b153c4e15cb885643193 | OFAC SDN list | 4 | inbound |
| Funds reaching this address are 2 hops from documented incident (0x356956…a99999).0x3569563839c4e308f09122126b4fad3ecaa99999 | documented incident | 2 | inbound |
| Funds reaching this address are 2 hops from documented incident (0xa9cfc9…5cf9a0).0xa9cfc982a66d0134fee2539cfd633559fb5cf9a0 | documented incident | 2 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x09155e…4dbe62).0x09155e8cbb30b34a0fdc65e8419d6c9d684dbe62 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x0ee6b0…ad0fb4).0x0ee6b037ac4f526f9a47936c4cafc52037ad0fb4 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x137fcc…57af78).0x137fcc71e3be35b45e6246e5f3cdcff2c457af78 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0xac8f8a…2efaa3).0xac8f8a4f693c6bef022d31936fb75e12172efaa3 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x26538c…ac382f).0x26538ce2b878b022e728fab851ed8beb1eac382f | documented incident | 3 | inbound |
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.