Every token launch on Solana leaves a complete, permanent, public record of exactly what happened. Who deployed it. Which wallets received tokens. How much liquidity was added and by whom. Whether the deployer has done this before. All of it is on-chain, and all of it is readable — in seconds, once you know what you are looking at.
Automated safety scoring handles this at the speed required for sniping. But understanding what the data actually says makes you a better operator: you'll calibrate your filters more intelligently, recognise when to override the score, and understand why certain tokens behave the way they do after launch. This knowledge also pairs directly with the rug pull warning signs checklist — most of those signals are on-chain and readable with the tools covered here.
Why On-Chain Data Tells a Different Story
A token's website can say anything. The social media account can be a week old with purchased followers. The whitepaper can be copy-pasted from a different project. None of that matters once you look at the blockchain record, because the blockchain cannot lie and cannot be edited.
On-chain data reveals:
- Whether the deployer has launched tokens before, and what happened to them
- Whether the liquidity was actually locked or just claimed to be
- Who bought in the first block — bots, the deployer themselves, or genuine outside wallets
- Whether any wallets received large token allocations before the pool was publicly visible
- Whether the token contract has unusual permissions that could be used maliciously
The mechanics of how a sniper bot reads the blockchain — subscribing to program logs via WebSocket — is the same mechanism you can use manually to audit any token in real time.
Tools for Reading Solana Data
Solana Explorer (explorer.solana.com)
The official block explorer. Best for reading raw transaction data, account states, and program logs. Less user-friendly than alternatives but gives you the most complete picture of what actually happened in a transaction.
Solscan (solscan.io)
The most widely used third-party explorer. Provides readable decoded instruction data, token holder lists, account funding history, and transaction success/failure rates. Essential for holder distribution analysis.
Birdeye / DEX Screener
Price chart tools with integrated on-chain annotations. Useful for seeing buy/sell patterns overlaid on the price chart — large sells from a single wallet show up visually alongside the price action they caused.
The sniper bot's own data panel
The Solana Sniper Bot surfaces key on-chain signals directly in the token detection feed — safety score breakdown, deployer wallet age, top holder percentages, and authority status — without requiring you to switch to an external explorer mid-launch.
Reading Pool Transactions
The pool creation transaction is the single most information-dense event for a new token. Find it by searching the Raydium AMM program address on Solscan and filtering for recent pool initialisation instructions, or by searching the token's mint address directly.
What to check in the pool creation transaction
Signer (deployer) wallet: The wallet that paid for pool creation. This is your primary investigation target. Note the address and open it in a separate Solscan tab.
Initial SOL amount: How much SOL was deposited to create the pool. Lower than 3 SOL on a token claiming to have community backing is a mismatch worth noting.
Token amount deposited: Combined with the SOL amount, this sets the opening price. An unusually small percentage of total supply in the pool compared to the dev wallet means the developer holds massive unrealised supply outside the pool.
Timestamp: When the pool was created relative to when social media accounts started promoting the token. Pre-launch marketing that started before the pool existed is normal. Marketing that started after the pool had already been live for hours without anyone noticing is unusual — it may indicate the developer is artificially creating activity after a quiet initial launch period.
First buyer transactions
Examine the first 5–10 buy transactions after pool creation. Key questions:
- Were they all submitted within the same block? Multiple coordinated buys in the same block from different wallets, all funded from the same source, indicate the developer is buying their own token to inflate the starting price.
- Do the buyer wallets have any prior transaction history, or are they fresh wallets created in the same session?
- What size were the first buys? Very large first buys relative to pool liquidity cause the price to spike before the majority of buyers can enter — this is sometimes intentional to create a FOMO chart shape.
The first 30 seconds of on-chain activity tells you more about a token's legitimacy than the next 30 days of social media content. If the first block looks coordinated, treat the token as compromised regardless of other signals.
Analysing the Deployer Wallet
Open the deployer wallet address in Solscan and look at its full transaction history. You're building a picture of who this entity is and what they've done before.
Wallet age
When was this wallet first funded? A wallet created within the last 24–72 hours has no track record. That alone is not a red flag — everyone has a first transaction — but combined with other signals it matters. A wallet that has been active for months or years on Solana carries more credibility.
Previous token deployments
Has this wallet deployed other tokens? Search for SPL token creation instructions in the wallet's history. If there are previous tokens, look them up. Did they survive? Did the liquidity get removed? Are there many failed tokens followed by a small withdrawal pattern — the signature of a serial rug operator?
Interaction history
A legitimate developer typically has a diverse on-chain history: DeFi interactions, NFT activity, multiple DEX protocols, payments to services. A wallet that only ever creates tokens and moves SOL in and out is a throwaway wallet built for a specific purpose.
Current SOL balance
A developer who just launched a token and already has a large SOL balance may have profited from previous launches — check where that SOL came from. Conversely, a wallet with near-zero balance that just created a pool may be operating with the minimum required funds, suggesting this is a low-investment, throwaway operation.
Reading Holder Distribution
On Solscan, open the token page and navigate to the Holders tab. This shows the top wallets by token balance as a percentage of total supply.
Concentration analysis
Add up the percentages of the top 10 holders. If the top 10 hold more than 40–50% of supply collectively, the token is highly concentrated. Any of those wallets selling meaningfully will affect price. If a single non-deployer wallet holds more than 5–10%, investigate that wallet — it may be an undisclosed insider allocation.
Wallet cluster detection
Open the top 5–10 holder wallets in separate tabs and check each one's funding history. Were multiple holder wallets all funded from the same parent wallet in a short time window? This is the cluster pattern described in the safety checklist — it indicates the developer has distributed tokens across multiple controlled wallets to hide concentration.
Bot wallet patterns
Early buyers that are clearly bot wallets (created recently, no history, small SOL balance, only DEX swaps) are not necessarily malicious — they may be competing sniper bots. But a high percentage of bot wallet holders with no genuine human buyers suggests the token has no real community, only automated buyers who will exit as soon as they hit take-profit.
Token Account Flags: Freeze and Mint Authority
On the Solscan token page, the Overview section shows the token's mint authority and freeze authority status. These two fields are binary: either the authority is held by a specific address, or it has been set to null (revoked).
Mint authority
If this field shows any address other than null, the holder of that address can create new tokens. New supply dilutes existing holders proportionally. Even if the dev wallet currently holds only 5% of supply, with active mint authority they can print themselves to 90%. Revoked mint authority is a non-negotiable requirement for the conservative strategy profile and strongly recommended for balanced.
Freeze authority
If active, this allows the freeze authority holder to lock any wallet's token account, preventing transfers. You could buy a token and find yourself unable to sell because the developer has frozen your account. Some legitimate stablecoin issuers retain freeze authority for regulatory compliance purposes, but for a meme token or new DeFi project, there is no legitimate reason to keep freeze authority active.
Putting It All Together: A 90-Second Token Audit
In practice, you rarely have more than 60–90 seconds to make a sniping decision before the early entry window closes. Here is a prioritised audit sequence that covers the highest-signal checks first:
- Freeze and mint authority (10 seconds): Open Solscan token page. If either is active, decision is made — skip unless you have a specific reason to override.
- Top holder concentration (20 seconds): Check top 5 holders. Any single wallet above 15%? Any cluster pattern visible? If yes, note and factor into position size.
- Deployer wallet age (15 seconds): How old is the deployer wallet? Previous tokens? If it's a fresh wallet with no history, reduce position size accordingly.
- First block buyers (20 seconds): Look at the first 3–5 transactions after pool creation. Coordinated wallets? Massive initial buys? Fresh wallets buying identical amounts?
- Liquidity lock status (15 seconds): Is pool LP locked? For how long? Single LP provider or multiple?
The automated safety score in the sniper bot strategy compresses all of these checks into a single number that updates in real time. But knowing what that number is actually measuring makes you a substantially better operator — you can override it intelligently, calibrate your thresholds with real understanding, and spot the edge cases where the automated check misses something the data makes obvious.