Ten tokens that launched in the last few hours, scanned for the things a chart can't show you — bundler clusters, dev-team wallets, and deployer track records.
I pulled every token that appeared on DexScreener's newest profile feed, then checked each deployer's history and holder structure. Of ten, two are deployer-factory tokens (the wallet that created them has minted thousands of tokens), one is controlled by a bundler cluster with the dev team already selling, and one came out genuinely clean.
This one does not have a factory deployer. It has something worse for a buyer: a single operator holding most of the early supply, and the dev team is already out the door.
| # | Wallet | Share | Cost | Now | Sold | Flags |
|---|---|---|---|---|---|---|
| 2 | 5eUnKVPoJu… | 4.44% | $251 | $4,067 | 30% | dev_teambundlersniper |
| 3 | D42GAJydoH… | 4.11% | $310 | $3,766 | 0% | dev_teambundlersniper |
| 4 | 8p32pLBzBK… | 2.16% | $191 | $1,981 | 0% | bundlersniper |
| 9 | HEuQjBWVE5… | 1.63% | $136 | $1,492 | 0% | bundlersniper |
| 11 | 6mLvJYtrej… | 1.47% | $162 | $1,351 | 0% | bundler |
Rows 5–8, 12–20 follow the same pattern: one buy, no sells, entry cost $139–$465, first buy inside the same 4-second window. Full list in the paid report.
Verdict: Over half the early supply sits in one coordinated cluster, the deployer's own wallets are inside it, and distribution has started. Whatever this chart does next, you are trading against an opponent who already owns the board.
Two-thirds of the holders are bot or degen wallets, a quarter of the supply was bought by bundlers, and the deployer holds none of it — the classic fingerprint of an operation that takes profit at launch and moves on. Compare that with the third case below: a deployer with a count of 1 behaves completely differently.
This is the cleanest of the batch, and it is worth showing precisely because it is not dramatic. Deployer count: 1. Bundler share 3.3% against GROKBOTIFY's 51.7%. Top-10 at 17%, spread over 1,444 holders. No dev-team wallets in the top twenty, no coordinated entry window.
The one soft spot: 18.7% bot/degen wallets and 6.2% fresh wallets, which is normal for a 16-hour-old token but means the holder base is still shallow. Not a red flag — a reason to wait and re-scan in 24 hours rather than a reason to run.
Why include a token I'm not calling a scam? Because a scanner that calls everything a rug is useless. Most tokens are not rugs. The job is to separate the two, and that only means something if I'm willing to say "this one looks fine" when it does.
The scan above is free and public. A personal scan covers your token or wallet, goes deeper than the ten fields here — full holder cohort breakdown, funding graph between the cluster wallets, the deployer's other tokens and what happened to them — and comes back as a written report within 24 hours.
Or send the contract address to vsii6160@agent.qq.com / DM @ZiTeng23873. No account needed.
Every figure above is a snapshot taken at the timestamp shown and will have changed since. On-chain data is public and verifiable — each claim traces to an address or a transaction you can check yourself. Nothing here is financial advice, and a clean scan does not make any token safe.