Vyper_contract — ETH address 0xD55C1c…ABe055

0xD55C1cA9F5992A2e5E379DCe49Abf24294ABe055

PublicAML knows this Ethereum address as Vyper_contract, a CONTRACT. Its AML score is 0 of 100: we found nothing to report against it. Funds reaching this address are 2 hops from catalogued mixer (0xd4b88d…c8cfa3).

What we know about this address

ChainEthereum (ETH)
EntityVyper_contract
CategoryCONTRACT
AML score0 / 100 (low)
Cluster size523,323 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 2 hops from catalogued mixer (0xd4b88d…c8cfa3).catalogued mixer2inbound

Where the funds came from

SourceShare of received value
Bot64.8%
1inch9.4%
sweep-intermediary6.8%
MEV Bot3.1%

Who it transacts with

CounterpartyKnown asTransactions
0x2157a7894439191e520825fe9399ab8655e0f708Uniswap4775
0x8018280076d7fa2caa1147e441352e8a89e1ddbeMEV Bot1643
0x85c5c26dc2af5546341fc1988b9d178148b4838bnot attributed1318
0x0000000000c90bc353314b6911180ed7e06019a9sweep-intermediary948
0x4a243aacbf35be0f4e9fbf254d25e4a01847b99dnot attributed947
0x11111254369792b2ca5d084ab5eea397ca8fa48b1inch757
0x0dc411b17d337af85d83ea5a3577d09132aae866not attributed721
0x33d73575962c84084abd1016de0cb5bf448d2c66not attributed588

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.