Moopy — ETH address 0xeEE01E…5cEeE3

0xeEE01E9364C2bF5AfF24328FB5bDFb98fF5cEeE3

PublicAML knows this Ethereum address as Moopy, a CONTRACT. Its AML score is 0 of 100 because we treat this address as infrastructure (known CONTRACT — 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 6 hops from OFAC SDN list (0xdcbeff…643193).

What we know about this address

ChainEthereum (ETH)
EntityMoopy
CategoryCONTRACT
AML score0 / 100 (floored from 25, 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 6 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list6inbound
Funds reaching this address are 6 hops from OFAC SDN list (0x9be599…a15573).OFAC SDN list6inbound
Funds reaching this address are 6 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list6inbound

4 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
unknown37.8%
@susuprior0.7%

Who it transacts with

CounterpartyKnown asTransactions
0xa4c7873a7f75d054a2d7720d2c00cf998147b2d6not attributed23
0x1a25285541f42acec35b76664a7f68f6288a9b16not attributed21
0x7293722ca3e1329a481dc5f91f96288e127e6156not attributed15
0xdbe696c3754157550754677932f6f5a54ae89863not attributed13
0xd0446a39c9ac3db0be9a5e4a06d55a7129c961c9not attributed12
0x120eb1488b59b0dac00c2e4a819094128a9f4e96not attributed11
0x97edf63009f01c259943595e65275c0a74ec9efanot attributed11
0xff362f8669136327ecddb191a2e3213c717f0b38not attributed11

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.