Uphold — BTC address 1CX3Ty5T…LGNXYB

1CX3Ty5T9XLvkqe6HV56YmbVkyHjLGNXYB

PublicAML knows this Bitcoin address as Uphold, a cex. Its AML score is 0 of 100 because we treat this address as infrastructure (known cex — infrastructure, indirect exposure 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 6 hops from documented incident (14aa9hF5…jgMwGX).

What we know about this address

ChainBitcoin (BTC)
EntityUphold
Categorycex
AML score0 / 100 (floored from 46, treated as infrastructure)
Cluster size42,093 addresses

Risk findings

Each row carries the source that flagged it. A row at zero hops names this address directly; any other row is a path our propagation engine traced from a flagged address to this one. A finding is an observation about the flow of funds or about a published listing, not a statement about the owner of this address.

FindingSourceHopsDirection
Funds reaching this address are 6 hops from documented incident (14aa9hF5…jgMwGX).14aa9hF5VEuxT8uUArbAt5KRMBmhjgMwGXdocumented incident6inbound
Funds reaching this address are 6 hops from documented incident (198ydM7h…ZjsJMa).198ydM7h954kk4za9wFr594Kc2bpZjsJMadocumented incident6inbound
Funds reaching this address are 6 hops from documented incident (1HY1cxkZ…57ahgV).1HY1cxkZiGMtR4Ev1T5j3fPiFWLF57ahgVdocumented incident6inbound
Funds reaching this address are 6 hops from documented incident (1Hg7NvnQ…w29ZKk).1Hg7NvnQbAdrp2BmhZeaz1kri5UUw29ZKkdocumented incident6inbound
Funds reaching this address are 6 hops from documented incident (1Ne1f1ib…XBPFZ6).1Ne1f1ibF4BgfytbJDQCRTwmMSg1XBPFZ6documented incident6inbound
Funds reaching this address are 8 hops from documented incident (15QUGrDs…VKUG7G).15QUGrDsjJ9ikLT6T1QbNR1wXg5UVKUG7Gdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (15ahnmQE…fsYaWd).15ahnmQEsWFakMkJef68aP2xhfwnfsYaWddocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (15qVTezG…hiVVTB).15qVTezGX8oe59u8qfnv3iqB55nshiVVTBdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16SA4xR1…Q1zFaY).16SA4xR1h9HFvc8W9hPozuq1LxHGQ1zFaYdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (15Qhc2y2…vmFwa5).15Qhc2y2EnkGAbFeDVS93f7ECbJBvmFwa5documented incident8inbound

More addresses in this index

These are other addresses in the PublicAML directory, not counterparties of this one. Nothing here implies a connection between them.

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

See something wrong on this page? Tell us and we will check it.

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.

Is this your address?

Leave your email and we will watch this address for you: you hear from us when money moves through it or when what we know about it changes. We cannot recover anyone’s money, and we will not pretend otherwise — but you will not have to keep checking.

We use the address only to reach you about this wallet. No password to choose: you sign in with a code we email you.

If you want to put the whole account on record — what happened, when, how much — file a report. We never publish who filed one.