HTX — ETH address 0x2Abc22…EfeB6A

0x2Abc22eb9A09EbBE7b41737CCde147F586EfeB6A

PublicAML knows this Ethereum address as HTX, a cex. Its AML score is 0 of 100 because we treat this address as infrastructure (known cex — 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 2 hops from catalogued mixer (0x169ad2…15d52b).

What we know about this address

ChainEthereum (ETH)
EntityHTX
Rolehot wallet (per arkham)
Categorycex
AML score0 / 100 (floored from 18, treated as infrastructure)
Cluster size261,208 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 2 hops from catalogued mixer (0x169ad2…15d52b).catalogued mixer2inbound
Funds reaching this address are 2 hops from catalogued mixer (0x23773e…f25334).catalogued mixer2inbound
Funds reaching this address are 3 hops from catalogued mixer (0xd4b88d…c8cfa3).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x4736dc…cfba9d).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0xfd8610…6c7144).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x610b71…5ceab4).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x178169…ddd0f1).catalogued mixer3inbound

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
unknown64.1%
HTX16.2%
exchange-deposit0.8%

Who it transacts with

CounterpartyKnown asTransactions
0x8e5a6e6fb4926284774a437241769f9b30c2f743HTX6801
0xdb8c7d59198c68f28f78689406e1a36064fa3ec3not attributed1780
0xcba87910b32c98b78aee87718252e5a95d20fe93not attributed1580
0xc585ad419c5650041b74b105075248f80ac9135dHTX738
0x7672bbdc87614f65e765e7c17d126e4f5c3b4af0not attributed735
0xfe0c707eea0e379447a7866fb4fdc16f6c8081d0HTX615
0x6e850b0e72ef3ebb55647919c6f17bdcca8a18d8not attributed556
0x924175a7ce9808cd9da18d152dc8c13fd28757a5not attributed495

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.