GDEXRouterV11 — ETH address 0xF89Dc5…6E9E64

0xF89Dc5519C2BfDc3dab5BE2F7803dfb2E16E9E64

PublicAML knows this Ethereum address as GDEXRouterV11, 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 4 hops from OFAC SDN list (0x9be599…a15573).

What we know about this address

ChainEthereum (ETH)
EntityGDEXRouterV11
CategoryDEX
AML score0 / 100 (floored from 55, treated as infrastructure)
Cluster size163,582 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.

FindingSourceHopsDirection
Funds reaching this address are 4 hops from OFAC SDN list (0x9be599…a15573).OFAC SDN list4inbound
Funds reaching this address are 4 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list4inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x95584c…84eae3).OFAC SDN list5inbound

7 further internal signals are held back from this page. They come from heuristics with known false positives, and we do not publish an accusation we would not defend. They are visible in the live check.

Where the funds came from

SourceShare of received value
unknown100.0%

Who it transacts with

CounterpartyKnown asTransactions
0x932bf0a8746c041c00131640123fa6c847835d6fnot attributed557
0xd9e1ce17f2641f24ae83637ab66a2cca9c378b9fSushiSwap322
0xd840b263bed70c8ef3728ddcae64d482e7fdd513not attributed226
0xfd1d68c4748100e63b22ab6e75d8d41444418961not attributed53
0x02c8693c096ddd889a23c34acaaf4c355cbbdc0dnot attributed52
0x39b69ed9cee77103cf1629ee7c5f5ff1c5af2656not attributed51
0x96ff693f02dad60635e43be98ae2c4d905f203acnot attributed40
0x3d78012c0f20742c9a45f598fc3d8521b1d4cbd0not attributed37

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.

Contact us about this address

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.