TruScan reads public Solana data for the contract you paste. Every check passes, needs attention or couldn’t be read. None of them rates the token as a whole.
Start with one observation. Confirm the contract address, then read the reason attached to each result. A familiar name doesn’t identify a token. Check counts describe the checks that apply, without an overall verdict.
Reading a scan, step by step →Mint, freeze, transfer features and the name: who can change the token, and what can affect transfers.
The largest wallets as one figure, and the identified creator wallet as a check. Bubblemaps shows how wallets connect.
The curve’s reserves and the asset received when selling.
Only the contract address identifies a token, not its name.
Choose “Run Deep Dive” to explore a pump.fun launch’s opening minute, current balances for selected launch wallets, funding connections and the creator’s other tokens. These observations don’t change the contract-check counts.
The launch view reads up to 500 earliest transactions. If those aren’t available, it reads up to 24 transaction details instead. Missing records are marked incomplete, and some history can remain outside this bounded read. The opening-minute trades are from pump.fun; later creator movements are shown separately.
The snapshot separates launch purchases from later balances. Buyer counts exclude the creator. Each balance figure says how many wallets were checked; it is not a view of every holder. Open a timing row to inspect the buyers and their purchase transactions.
Purchase percentages use the supply at launch and include repeat buys. Current balances have their own observation time. They do not show how much of an original purchase was kept or sold. Wallets that signed a purchase are listed separately when they differ from the buyer; a signature can include fee sponsorship.
Creator buys and sells include later trades in the records already read; the result says how far that reaches. The earliest records of the creator’s token account show movements out: a sale on any venue (the creator received SOL), a transfer to another wallet, a burn, or tokens moved into a program account such as a pool. A transfer shows tokens moving, not who controls the receiving wallet.
“Check funding connections” inspects up to twelve launch wallets and their first eight successful transactions. Shared source addresses describe transfers, not common ownership. Known services such as Relay are kept out of wallet connections. Shared fee payers require wallet signatures; shared SOL recipients require transfers in the same minute. This sample does not cover later trading or all wallets and funding routes.
“Explore other tokens” reads up to 500 earliest creator transactions, keeps up to twenty observed launches by creation time and compares up to six other launches for recurring buyers and purchase signers. Launches this wallet signed for a different creator are marked separately. The five cards come from that returned sample, highest available market cap first, not every token the wallet ever launched. Names come from creation records or DEX Screener, and market caps from DEX Screener; missing names, pictures and market caps stay unavailable. Supported legacy creations and CreateV2 records are included. Wallet links open pump.fun or Solscan when you want to explore further.
For wallets funded through the Relay bridge, the request ID in the transfer’s memo is matched against a deposit on Robinhood Chain, with its sender and transaction evidence. Shared verified deposit addresses are shown as observed connections. An unresolved lookup leaves the origin unknown.
Figures from outside providers, shown beside the checks. They don’t change any check.
See Privacy for what each provider sees.
Technical references: Solana transactions ↗ (opens in a new tab) · Jupiter route sizing ↗ (opens in a new tab)
