@yogurt_eth — ETH address 0x98e0b0…C55584

0x98e0b03e9a722B57CE97EEB0eb2930C6FeC55584

PublicAML knows this Ethereum address as @yogurt_eth, a individual. Our AML risk score for it is 40 of 100, which we read as medium risk. Funds reaching this address are 5 hops from sanctioned entity (Arkham) (0x475664…a704f2).

What we know about this address

ChainEthereum (ETH)
Entity@yogurt_eth
Categoryindividual
AML score40 / 100 (medium)
Cluster size86 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 5 hops from sanctioned entity (Arkham) (0x475664…a704f2).sanctioned entity (Arkham)5inbound
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 4 hops from attributed to a hacking entity (Arkham) (0x1342a0…78bd5f).attributed to a hacking entity (Arkham)4inbound

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
Uniswap100.0%
deBridge Finance0.0%
unknown0.0%
MEXC0.0%
Shuffle.com0.0%
MetaMask0.0%

Who it transacts with

CounterpartyKnown asTransactions
0x00000000006c3852cbef3e08e8df289169ede581OpenSea2727
0xfcc926dfef1548a8e74c36d1b0d3c05f13b60918not attributed380
0x74312363e45dcaba76c59ec49a7aa8a65a67eed3X2Y2362
0xb43a210779d62a2c0fb06b0cd808b65fe22b9676not attributed331
0x791797e5d63e42022bcca8bf59645c4453fb7587not attributed322
0x44e94034afce2dd3cd5eb62528f239686fc8f162Manifold322
0xfe500c274f72f1d1a9978c903d97e6d45cd9121bnot attributed321
0xb62ff26cade8d13dbf5bbf7d12e66d3add8fc125not attributed295

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.