ETH address 0x4f6404…720Ea4

0x4f64046ee0F7c6e1d774dD5341C3caA857720Ea4

PublicAML knows this Ethereum address as a deposit address. Its AML score is 0 of 100 because we treat this address as infrastructure (known deposit — 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 11 hops from sanctioned entity (Arkham) (0x475664…a704f2).

What we know about this address

ChainEthereum (ETH)
Categorydeposit
AML score0 / 100 (floored from 25, treated as infrastructure)
Cluster size233,997 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 11 hops from sanctioned entity (Arkham) (0x475664…a704f2).sanctioned entity (Arkham)11inbound

Where the funds came from

SourceShare of received value
HTX82.6%
unknown17.4%
sweep-intermediary0.0%

Who it transacts with

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.