ETH address 0x46e910…E34Fe1

0x46e910953D4Bb7d32E630aB9d45f56E4AFE34Fe1

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 3 hops from OFAC SDN list (0x098b71…3e2f96).

What we know about this address

ChainEthereum (ETH)
Categoryconsolidation
AML score0 / 100 (floored from 70, treated as infrastructure)
Cluster size1,206,009 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 3 hops from OFAC SDN list (0x098b71…3e2f96).0x098b716b8aaf21512996dc57eb0615e2383e2f96OFAC SDN list3inbound
Funds reaching this address are 4 hops from OFAC SDN list (0xdcbeff…643193).0xdcbeffbecce100cce9e4b153c4e15cb885643193OFAC SDN list4inbound
Funds reaching this address are 5 hops from sanctioned entity (Arkham) (0x475664…a704f2).0x475664cdedb4ffaf34a81c2a83e2c09417a704f2sanctioned entity (Arkham)5inbound
Funds reaching this address are 3 hops from attributed to a hacking entity (Arkham) (0x000056…100000).0x000056c346441ef8065e56b0cddd43fdec100000attributed to a hacking entity (Arkham)3inbound
Funds reaching this address are 2 hops from catalogued mixer (0x4736dc…cfba9d).0x4736dcf1b7a3d580672cce6e7c65cd5cc9cfba9dcatalogued mixer2inbound
Funds reaching this address are 3 hops from catalogued mixer (0xd4b88d…c8cfa3).0xd4b88df4d29f5cedd6857912842cff3b20c8cfa3catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x169ad2…15d52b).0x169ad27a470d064dede56a2d3ff727986b15d52bcatalogued mixer3inbound

2 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.

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.