Docs

How to read a scan.

Catalyst takes a Solana contract address (CA) and rebuilds the story of how the coin grew. This page explains what every section means, how the signals are detected, and where the limits are.

Quick start

Open the app, paste any Solana CA, and press enter. Market data loads first, then the other layers fill in as their APIs answer: X, wallets, holder labels, pump.fun. Want to see the layout without using any API? Open the demo, which runs on synthetic data.

  1. Read the chart and the growth read for the short version of the run.
  2. Scroll the timeline to see each catalyst with the wallets, callouts and posts around it.
  3. Open Playback to watch the whole run replay in a terminal.
  4. Open Narrative for the story in words, with sources.

How catalysts are detected

Market cap

Market cap on the chart is each candle's close multiplied by supply. Supply is taken from the current price and market cap (or FDV) at the time of the scan, so historical market cap is an estimate. If the token minted or burned supply later, early values will be off.

Candle size

Catalyst picks resolution from the pair's age: 1-minute and 5-minute candles under 36 hours old, hourly under 40 days, daily after that. Younger coins get finer detail.

New ATHs

Every time market cap closes above its previous high it is a candidate ATH. To keep the chart readable, Catalyst only keeps breakouts that are meaningfully bigger than the last one (starting at 1.35×, raised automatically until there are about 11 markers). The final marker is the all-time high.

Volume surges and ignition

The baseline is the trailing median volume. A candle is a surge when its volume is at least 3× baseline and at least $1,000. Neighbouring surge candles merge into one zone. Ignition is the first zone where market cap also moved at least 30%: the moment volume and price took off together.

Social impact windows

For each post or callout, Catalyst measures how much market cap rose in the window after it (24 hours on fine candles, otherwise two candles) and how volume compared with just before. This shows timing, not cause. A post that lands right before a pump may have simply been first to notice it.

The sections, in order

#What it shows
01Chart. Market cap line, volume bars, shaded surge zones, ignition line, ATH pins, King of the Hill and graduation lines. Diamonds are posts, triangles are callouts, and ▲▼ along the bottom are tracked-wallet buys and sells. Click a marker to jump to it in the timeline.
02Growth read. Plain-language summary: launch, ignition, ATH ladder, callouts, current drawdown, best-timed post.
03Timeline. Every catalyst with its wallets, callouts and possible social trigger.
04Wallets. Top wallets by volume, earliest buyers and whether they still hold.
04+Holder mix and tracked wallets. Supply held by dev, insiders, bundlers, snipers and smart traders, plus your own watchlist.
05Pump.fun launch data. Creation time, creator, King of the Hill, graduation, coin-page comments.
06Pump.fun callouts. Who called it, at what market cap, how far it went after, and how many people tailed.
07Social. The project's X account, the highest-engagement posts and the earliest accounts to mention the CA or cashtag.

Wallets and tags

Wallet data comes from Helius swap history. Each swap is attributed to the transaction's fee payer, so a router, bundler or bot can hide the person who actually traded. Volume in USD uses the swap's SOL leg when available.

TagMeaning
devThe creator wallet reported by pump.fun,.
earlyOne of the first 15 buyers. Only shown when the launch window is inside the loaded history.
whaleOne of the three highest-volume wallets.
bot?150 or more trades. Likely automated, not proof.
sniper insider bundlerLabels for wallets that bought in the launch block, are linked to the dev, or were funded and bought as a bundle.
smart pro freshTrader categories: profitable history, active history, or a new wallet. These are heuristic categories.
Tags are context, not accusations. A wallet can be tagged because of how it was funded or when it bought, without any wrongdoing.

Tracked wallets

In the holder mix section, paste wallet addresses, one per line, with an optional label: 9xQeW…k3Lm my alpha wallet. Press Save. The list is stored in your browser only, so it does not follow you to another device.

Tracked wallets rely on Helius wallet history, so they appear whenever that history covers the coin.

Playback

Playback is a terminal timelapse of the coin's life. The head moves along an ASCII market cap chart with volume bars underneath, and pauses at each catalyst: ATH, ignition, surge, King of the Hill, graduation, callout, post and tracked-wallet move. A log line types out for each one. At the end it prints a summary.

Narrative tab and the cat

The Narrative tab turns everything found for the coin into a short story: phases, what people were saying, risks and what is missing. The tab cites the posts, callouts and comments behind each claim.

The ASCII cat walks you through a scan out loud. It starts once the data layers have settled, and you can pause it, skip, or minimise it.

What powers it

Catalyst reads three live sources and combines them into one timeline.

SourceAdds
pump.funCallouts and caller profiles, who tailed each call, holders and top-trader trades, the creator, bonding curve vs graduated, King of the Hill, coin-page comments
HeliusWallet-level swap history: top wallets, early buyers, the wallets behind each catalyst, tracked wallets
XThe project account, viral posts, mentions and the earliest accounts to call it

Price and volume candles are pulled alongside to draw the chart and run the catalyst math.

Limits and honesty notes

FAQ

Which coins does it work on?

Any Solana token with a trading pair. Pump.fun coins get extra data (creator, King of the Hill, graduation, callouts). A coin still on the bonding curve with no AMM pool yet may show little.

Why is a section empty?

Usually that data source had nothing for this coin or was briefly unavailable. The empty state says which.

Why did I get "scan limit reached"?

The server limits scans per visitor per hour to protect API quotas. Wait a while and try again.

Where do I follow updates?

On X: @Catalystca7.