YoBit — BTC address 1JafcHt5…p54gmV

1JafcHt5jMG9u66S3uHC65LGcBLop54gmV

PublicAML knows this Bitcoin address as YoBit, 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 8 hops from documented incident (15NYdfvS…pxdw53).

What we know about this address

ChainBitcoin (BTC)
EntityYoBit
Categorycex
AML score0 / 100 (floored from 37, treated as infrastructure)
Cluster size5,643 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 8 hops from documented incident (15NYdfvS…pxdw53).15NYdfvSatUTn44f42GtisTyN1fGpxdw53documented incident8inbound
Funds reaching this address are 8 hops from documented incident (15d3LaYt…tS7Jf3).15d3LaYtmTNsQ2Hrea78TstNRCcetS7Jf3documented incident8inbound
Funds reaching this address are 8 hops from documented incident (15psdyYh…V7GST4).15psdyYhyssnVoPF6LBjPLKpwzVuV7GST4documented incident8inbound
Funds reaching this address are 8 hops from documented incident (15xE77us…nKqXqU).15xE77usdqgjRdqEfgKYLezcvkxgnKqXqUdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16Di6hA8…C64P7R).16Di6hA8MH3dQAQMJ1hD1k7jcxKzC64P7Rdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16E2cnDB…QQq3cz).16E2cnDBBGj6nywFUYQoagypG76CQQq3czdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16LZePS7…h8j8TR).16LZePS7S9XEy22NJFqkv8hajCFjh8j8TRdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16Zr5YPz…soJv5o).16Zr5YPzVNBcVFbyWFcunf6Vcr3XsoJv5odocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16cVC6S4…JHTknB).16cVC6S4LvngsaoH9g89PYCSPgKGJHTknBdocumented incident8inbound
Funds reaching this address are 8 hops from documented incident (16k3TE9F…UhideB).16k3TE9FiF8ho6Un35JRDYmJPqVkUhideBdocumented 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.

1JafcHt5…p54gmV (YoBit) BTC address check | PublicAML