ETH address 0xC3Bb73…909E5b

0xC3Bb7346Bbf0bf300e11385FE402FE5fa6909E5b

PublicAML knows this Ethereum address as a consolidation address. Its AML score is 0 of 100 because we treat this address as infrastructure (known consolidation — 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 3 hops from OFAC SDN list (0xf2235d…2e27cb).

What we know about this address

ChainEthereum (ETH)
Categoryconsolidation
AML score0 / 100 (floored from 70, treated as infrastructure)
Cluster size1,990,854 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 3 hops from OFAC SDN list (0xf2235d…2e27cb).OFAC SDN list3inbound
Funds reaching this address are 4 hops from OFAC SDN list (0x95584c…84eae3).OFAC SDN list4inbound
Funds reaching this address are 5 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list5inbound
Funds reaching this address are 7 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list7inbound
Funds reaching this address are 7 hops from OFAC SDN list (0x5a7a51…a3b59f).OFAC SDN list7inbound
Funds reaching this address are 10 hops from OFAC SDN list (0x532b77…8b0e8a).OFAC SDN list10inbound
Funds reaching this address are 10 hops from OFAC SDN list (0xdb2720…ada8fe).OFAC SDN list10inbound
Funds reaching this address are 10 hops from OFAC SDN list (0xe3d35f…0dbca5).OFAC SDN list10inbound

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
Uniswap93.4%
1inch4.8%
Relay.link1.5%
OpenSea0.1%
unknown0.1%
@fangksbin0.0%
MEXC0.0%
Hyperunit0.0%

Who it transacts with

CounterpartyKnown asTransactions
0x0000000000000068f116a894984e2db1123eb395OpenSea1206
0x52708ab7cd90e02e1772cac49da6516b8d195a15not attributed286
0x527026c55d2bb2a144d2f436d5635b820f1e5a15not attributed280
0x00005ea00ac477b1030ce78506496e8c2de24bf5OpenSea256
0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2WETH67
0x00000000006c3852cbef3e08e8df289169ede581OpenSea48
0x0000a26b00c1f0df003000390027140000faa719OpenSea38
0x2103154710a5f033eb37d1a4f4f1771f8bd6ae3enot attributed32

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.