$ZAGS

How the launch buyers and top holders traded this coin (which app, which fee settings) and where the top holders' money came from. Read from each wallet's first trade of this coin.

Trading apps

Where the top holders' money came from

Apps are named only when the trade itself shows it (an account or program carrying the app's name, e.g. GMGN, Axiom, Jupiter); otherwise we show the wallet the trade paid a 0.1–3% fee to, or the program it went through. Priority fee = transaction fee minus the 5,000-lamport base per signature; a fee seen in 20+ other coins is marked as a common default. Exchanges are named only from our label book; a funder with 1,000 transactions in under a day is a busy hot wallet (exchange, swap service or bot). Facts, not part of the light. Measured 02 Nov 2026.

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.

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 01 Nov 2026.

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: 0.0%.

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.

• The teamOnly the dev wallet: no early buyer or holder wallets found with it. source
• Website doesn't show this token's addressThe token's address doesn't appear on its website or in the site's code; the site shows other addresses (0x3e…7777, 0xee…eeee, 0xca…ca11). source
• On-chain features in the codeThe site's code contains wallet or contract code. source
• Website age vs launchThe Internet Archive had no saved copy of the site (asked 2 h ago): it is probably as new as the coin.
• Same ticker elsewhere1 other coin trades as $ZAGS. None of them has real liquidity and trading behind its price. source
• Contract permissions (GoPlus)GoPlus finds none of the risky permissions it checks for. source
• Reused X accountThe X account @ZAG20AI is also listed by 2 other coins we checked: $ZAGS ×2. 2 of them came earlier. source
• Reused websiteThe website zag20.com is also listed by 4 other coins we checked: $ZAGS ×4. 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.