@xianyujiushiwo — ETH address 0xC5c6f9…e026b9

0xC5c6f9f0eA697c4727190da140BB776adae026b9

PublicAML knows this Ethereum address as @xianyujiushiwo, a individual. Our AML risk score for it is 55 of 100, which we read as medium risk. Funds reaching this address are 4 hops from OFAC SDN list (0x098b71…3e2f96).

What we know about this address

ChainEthereum (ETH)
Entity@xianyujiushiwo
Categoryindividual
AML score55 / 100 (medium)
Cluster size2,005 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 OFAC SDN list (0x098b71…3e2f96).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 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 (0x178169…ddd0f1).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0xd96f2b…364307).catalogued mixer3inbound

2 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
Gate28.4%
unknown19.7%
zkSync15.7%
Uniswap13.6%
Hop Protocol13.2%
OpenSea4.3%
WETH2.7%
LiFi1.0%

Who it transacts with

CounterpartyKnown asTransactions
0x7f268357a8c2552623316e2562d90e642bb538e5OpenSea200
0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2WETH93
0x7be8076f4ea4a4ad08075c2508e481d6c946d12bOpenSea77
0x74cdbf8944249a410f4a5200be0de81dccacd99bnot attributed49
0x0000000000a39bb272e79075ade125fd351887acBlur35
0xb2ecfe4e4d61f8790bbb9de2d1259b9e2410cea5Blur34
0x4c0f7076a86ab8b6e708490da6dacd3aca4a4735not attributed26
0xc64420157b83b9ca0b7e2a58b17676af16dfc55dnot attributed18

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.

0xC5c6f9…e026b9 (@xianyujiushiwo) ETH address check | PublicAML