ETH address 0x8675E4…a567E2

0x8675E4F59710c09b022E2b294551B7eD9fa567E2

PublicAML knows this Ethereum address as a consolidation address. Its AML score is 0 of 100 because we treat this address as infrastructure (known consolidation — 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 (0xf2235d…2e27cb).

What we know about this address

ChainEthereum (ETH)
Categoryconsolidation
AML score0 / 100 (floored from 55, treated as infrastructure)
Cluster size1,035 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 (0xf2235d…2e27cb).OFAC SDN list4inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x95584c…84eae3).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x931546…c8c568).OFAC SDN list5inbound
Funds reaching this address are 8 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list8inbound
Funds reaching this address are 8 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list8inbound
Funds reaching this address are 8 hops from OFAC SDN list (0x5a7a51…a3b59f).OFAC SDN list8inbound
Funds reaching this address are 8 hops from sanctioned entity (Arkham) (0x475664…a704f2).sanctioned entity (Arkham)8inbound

3 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
unknown91.1%
Binance6.8%
Legion1.6%
Dex Router (OKX)0.5%
StakeStone0.0%

Who it transacts with

CounterpartyKnown asTransactions
0x8888888199b2df864bf678259607d6d5ebb4e3ceCircle9555
0x8881f2c8d3c82a1eb88804351193109fd57f33eenot attributed84
0x097f24f74ecfbb7c075ee531c89991d8e62412dcnot attributed81
0x88888078f2d7e4034ab4cf0f35a6f742912ee3cenot attributed66
0x22e13b1731819715cde5cf7797bb3f0926cfd8b4not attributed65
0x5c60f46432bdf037679194fa0f0ec6d5776000b5not attributed64
0x1dc6997f110b73e580f7298dbdeaae0aa4e1c030not attributed58
0x4313c378cc91ea583c91387b9216e2c03096b27fGMGN41

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.