$SWAMIS

Groups of wallets that keep buying the same coins: launch crews (they buy launch blocks together) and holder guilds (they sit among the top holders of the same coins). Only groups with 2+ wallets in this coin.

The 4 wallets that bought in the launch block (the first two blocks, under a second) took 26.38% of the supply. Grouped by the wallet that first funded them: 1 linked group holds 25.16% of it.

Grey = a wallet with no funding link to the others. Taken out = sales minus buys plus liquidity out minus in, from the money-out measurement above.

The dev, the wallets that bought the launch block, and holders the dev funded: how they're connected and how their earlier coins did. The launch map below draws the connections.

Groups of wallets that keep buying launch blocks together, across coins we checked. A crew is a buying pattern; it doesn't say who runs it.

4 of the wallets that bought this coin's launch block also bought the launch block of other coins we checked. Sniper bots and launch groups both look like this.

Creator wallet 4TkhpkjeVPV3CdnLQTDJhMbxZAJmYUJ7RHNSPsHhd77e (from GeckoTerminal). No other coins from this wallet in our records yet. Open the wallet ›

Who each of the biggest holders is to this launch, from the launch block, first funding, insider flags, known groups and each wallet's first trade.

Source RugCheck, read 6 h ago.

The 20 biggest holders (bigger bubble = bigger share). Grey: pools and known services. Pink: wallets RugCheck flags as insiders. Same colour with a line to an outer dot: first funded by the same wallet. Liquidity locked: 100%.

Holders, insider flags, labels and liquidity locks: RugCheck. Shared funders: our own read of each wallet's first transaction.

The creator in the middle, the wallets that bought in the launch block around it (bigger bubble = bigger share of supply), and the wallets that funded them on the outside. Buyers with the same colour were funded by the same wallet.

What we find when we compare the coin's website, code, token, launch timing, liquidity, ticker and wallets against each other and against public address labels.

• Cabals in this coin2 known groups of wallets are in this coin. The largest, launch crew #7f9a2c, has 3 of its 4 wallets here: 25.16% bought in the launch block. 2 of the 4 coins it was in with an outcome fell 80%+ within a day. source
• Creator fees go to another walletThis coin's creator fees are paid to a wallet other than the one that launched it source
• The teamThe dev and 4 early buyer/holder wallets; 3 connected to the dev (funding or crew), holding 25.2%; their 23 earlier coins with an outcome: 14 fell 80%+, 0 went 2x+ within a day. source
• The story behind itThe coin's story is an X post by @ZzzzzSol (verified) with 14 likes. The post names this coin. 1 other coin we checked use the same post. source
• Website doesn't show this token's addressThe token's address doesn't appear on its website or in the site's code. source
• Website age vs launchThe Internet Archive first saved the site 7 years (2,677 days) before the coin launched. source
• Contract permissions (GoPlus)GoPlus finds none of the risky permissions it checks for. source
• Reused X postThe X post x.com/ZzzzzSol/status/2121552933271544138 is also listed by 1 other coin we checked: $SWAMIS. source
• Reused websiteThe website newreleases.io is also listed by 5 other coins we checked: $SWAMIS ×5. So many coins list it that it's most likely someone else's, borrowed for the story. source

How earlier coins with the same signals did: the share that fell 80% or more within 24 hours of our check, against coins without the signal. It describes past coins; it doesn't predict this one. All signals

• Checked isn't the same as safe: these checks describe what the token allows and what the website runs, not what anyone will do.
• "Nothing found" means not visible on the public page; servers and private code are invisible to us. Not financial advice.