On-chain verification
Every claim in the case file that touches the blockchain is verifiable independently. This page renders the relevant values fetched server-side from public, no-auth APIs at the time shown. Click any address to verify on Solscan or Pump.fun directly.
Ask an AI about this case
Each button opens an assistant with the question already filled in. It will read natro.meme and summarize what it finds — an independent way to check the record in your own words.
Opens in a new tab. The prompt is neutral and asks the assistant to cite its source. Answers are generated by the assistant, not by this site.
§ Token state
§ Holder distribution
Holder data temporarily unavailable
§ Insider clustering
RugCheck — an independent, automated Solana token scanner — flags large token movements between connected wallets it groups into "insider networks". The figures below are reproduced verbatim from RugCheck's public report for the token; they are algorithmic heuristics (BETA), suggestive of coordinated distribution rather than organic holding, and are not on their own proof of wrongdoing. On-chain forensic attribution is in progress.
| Insider network | Accounts | Moved | of supply |
|---|---|---|---|
| dazzling-sapphire-beaver | 170 | 369M | 37% |
| dazzling-garnet-beaver | 136 | 363M | 36% |
| lazy-coffee-newt | 48 | 228M | 23% |
| bitter-slate-squirrel | 174 | 208M | 21% |
| little-cinnamon-mouse | 37 | 118M | 12% |
| elastic-teal-ram | 62 | 115M | 12% |
Cluster shares overlap and are not additive — the same tokens can move through more than one network, so the percentages sum to more than 100%. RugCheck also marks the token's "Launch Insights" (BETA) as "Anomaly Found".
Two points on the record. First: RugCheck's aggregate "risk" score for the token reads low — but that score measures only technical rug vectors (mint authority revoked, liquidity-pool locked), not the marketing conduct or refund refusal documented elsewhere in this file; those are separate questions. Second: RugCheck still shows the creator wallet holding ~30M NATRO (3.0% of supply), consistent with the "founder bag" the project publicly committed to never moving. This file does not claim that bag has moved. Whether the clustered transfers above correspond to the named founder allocation or to separate team / insider allocations requires further on-chain forensics.
View the live RugCheck report ↗· 31 May 2026
§ Creator wallet activity
The wallet that minted $NATRO. Per the case file, relation to the publicly-stated "Alex's 3% bag" allocation requires further forensics — these are raw signatures, not interpretation.
Wallet: 76qavBCaqDzn6KP6q5Qzu5sXVUXSqXWQpCTTF6Tye7xx ↗
| Time (UTC) | Signature | Status |
|---|---|---|
| 2026-05-23 20:00 UTC | 446cNsFm…eZTicWvf ↗ | success |
| 2026-05-23 20:00 UTC | 3byV8qKu…P9ECUh2h ↗ | success |
| 2026-05-23 20:00 UTC | 2QRBL4v1…aBPaguDY ↗ | success |
| 2026-05-23 20:00 UTC | 4iLAVcPq…TV7UfcHR ↗ | success |
| 2026-05-23 20:00 UTC | BUSK7pEb…ouwsWaqR ↗ | success |
| 2026-05-23 20:00 UTC | 3PtCFDhM…jBiHtahx ↗ | success |
| 2026-05-23 20:00 UTC | 3iHs9HbG…k4kMbW25 ↗ | success |
| 2026-05-23 19:59 UTC | 4B8S3AhX…azs6cn51 ↗ | success |
| 2026-05-23 19:58 UTC | 3LZys1dT…ZvRXuKKj ↗ | success |
| 2026-05-23 19:58 UTC | 3zSj7ziA…yKZrnQUT ↗ | success |
| 2026-05-23 19:58 UTC | 2MnJ63eQ…HGwcJ6zL ↗ | success |
| 2026-05-23 19:58 UTC | 47aehD8z…uMtEnUeg ↗ | success |
| 2026-05-23 19:58 UTC | 3rfcAJ9x…nPkuBCbX ↗ | success |
| 2026-05-23 19:58 UTC | 2Mjpr579…KfhtPkSx ↗ | success |
| 2026-05-23 19:58 UTC | 3MUGNr5k…56Us5EQX ↗ | success |
§ Live market chart
Methodology
Token state and holder data are pulled from the Solana mainnet public RPC (`api.mainnet-beta.solana.com`). Market data is pulled from Pump.fun's public API (`frontend-api-v3.pump.fun`). Both are refreshed at most once per hour via Next.js ISR. No private keys, no paid API tier, no third-party aggregator that could shape the numbers.
If any block shows "API temporarily unavailable", the public source briefly rate-limited us — refresh the page in a few minutes. The case file's factual claims do not depend on this live verification rendering; the underlying blockchain state is independently checkable at any time via the linked addresses.