Binance — ETH address 0x00799b…e3079c

0x00799bbc833D5B168F0410312d2a8fD9e0e3079c

PublicAML knows this Ethereum address as Binance, 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 4 hops from sanctioned entity (Arkham) (0x475664…a704f2).

What we know about this address

ChainEthereum (ETH)
EntityBinance
Rolehot wallet (per arkham)
Categorycex
AML score0 / 100 (floored from 55, treated as infrastructure)
Cluster size1,373 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 4 hops from sanctioned entity (Arkham) (0x475664…a704f2).sanctioned entity (Arkham)4inbound
Funds reaching this address are 4 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list4inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x5a7a51…a3b59f).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list5inbound
Funds reaching this address are 4 hops from attributed to a hacking entity (Arkham) (0x1342a0…78bd5f).attributed to a hacking entity (Arkham)4inbound
Funds reaching this address are 4 hops from attributed to a hacking entity (Arkham) (0x04786a…f5ed90).attributed to a hacking entity (Arkham)4inbound
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

1 further internal signal is 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
unknown76.5%
exchange-deposit3.0%

Who it transacts with

CounterpartyKnown asTransactions
0x9cc5be83b211620cfe23e25bc65d6da6751bcf09Binance Deposit493
0xb3f923eabaf178fc1bd8e13902fc5c61d3ddef5bWintermute361
0xf05e2a70346560d3228c7002194bb7c5dc8fe100Jump Crypto311
0xf2103b01cd7957f3a9d9726bbb74c0ccd3f355d3not attributed269
0x141fef8cd8397a390afe94846c8bd6f4ab981c48Binance243
0x1671a3e4a2519a653e66e827ef6eae690ee86729Binance Deposit234
0x924cd9b60f4173dcdd5254ddd38c4f9cab68fe6bnot attributed198
0x345d8e3a1f62ee6b1d483890976fd66168e390f2Auros Global178

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.

0x00799b…e3079c (Binance) ETH address check | PublicAML