SUPPLY STRUCTUREFINALIZED RPC READS
Token accounts, not people
TOP ACCOUNTS
DOSSIER / STRUCTURE LENS / SOLANA BETA
See beyond
the ticker.
An evidence-led look at a token's controls, supply and ownership patterns. Every answer should show its source. Every gap should say unknown.
Enter a Solana mint for a fresh, read-only structure snapshot. The separate GFOF archive and historical movement case are dated and source-linked; the sample report is fictional. No wallet connection, automatic sale verdict, bundle accusation, safety rating or trading recommendation.
01 / LOOKUP
SOLANA FIRSTStart with the address
Explore a verified transaction Live lookup: mint structure only.
Checking the mint...
Submitted mint address
Mint controlsUnknown
Holder structureUnknown
Launch bundleNot checked
Reading finalized Solana account data. If the source is busy or incomplete, no report will be shown.
Inspect this address in Solana Explorer ↗SOURCE-BOUND SOLANA REPORT
READ-ONLY BETAWhat this mint shows now
SOLANA MINT
Observed account and mint facts, not a safety rating or a count of people. Results can be cached for up to five minutes.
TOKEN CONTROLSMINT ACCOUNT
Controls at capture
Recorded supply
Mint supply, not circulating or tradable supply.
Mint authority
Freeze authority
STILL UNKNOWNNOT CHECKED
What this cannot prove
Beneficial owners, launch bundles, sales, locks, liquidity and safety need separate evidence. A large or moving token account is not an accusation.
Bundle or sale findingNone made
ACCOUNT REGISTERUP TO 20 ACCOUNTS
Inspect the largest accounts
“Controller” is the token account's recorded authority. It may be a wallet or program and does not identify a person. A changed balance between the ranked and detail reads is marked.
SOURCE & LIMITS
Check the observation
Finalized Solana RPC methods: getAccountInfo, getTokenLargestAccounts and getMultipleAccounts. The report lists their slots. Source addresses open in Solana Explorer; independent re-ranking and history analysis are not performed.
01 Mint slot
02 Ranking slot
03 Detail slot
Open mint in Solana Explorer ↗Download this report JSON ↓02 / VERIFIED EXAMPLE
DATED EVIDENCEWhat the GFOF mint actually shows
CANONICAL SOLANA MINT
$GFOF
These are account and mint facts observed at recorded Solana slots. They are not a safety rating or a count of people.
SUPPLY STRUCTUREOBSERVED AT SOURCE SLOTS
Token accounts, not people
TOP 20 ACCOUNTS
TOKEN CONTROLSTHREE RPC SOURCES
Mint state at capture
Recorded supply
Units use six token decimals. Supply is not circulating supply.
Mint authority
No authority was present in the captured mint account.
Freeze authority
No authority was present in the captured mint account.
Both Solana's public RPC and PublicNode matched the Ankr mint fields at nearby finalized slots. These facts do not prove market safety or who controls other accounts.
STILL UNKNOWNNOT CHECKED
What this cannot tell us
Beneficial owners, launch coordination, Jito bundles, lock terms, liquidity and tradable supply require separate evidence. A common slot or a large token account is not a bundle verdict.
Bundle findingNone made
Movement after this capture has not been analyzed. A separate historical movement case examines three earlier transactions. An outgoing transfer alone is not a sale.
ACCOUNT REGISTERDATED SNAPSHOT
See the ranked accounts
Inspect all 20 token accounts and their controllers
Rank and share are from the dated capture. “Controller” is the token account’s recorded authority, which may be a wallet or program; it does not identify a person. Open either address to inspect its public activity.
03 / THE PROOF
Check the source
Ankr returned the ranked token accounts. Solana's public RPC independently matched all 20 account balances and owners at a later finalized slot; it did not independently re-rank every account. The downloadable JSON contains the methods, parameters, source responses and limits.
01 Mint slot
02 Top-account slot
03 Independent check slot
Read the source capture JSON ↗Open the mint in Solana Explorer ↗03 / FOLLOW THE FLOW
SOURCE-BOUND CASEWhere did these tokens go?
THE QUESTION
Transfer, then swap
Two token accounts sent GFOF to a third. That third account later swapped its full 15 million GFOF balance. The chain shows the route and asset received, not the people behind the accounts.
THE OBSERVED ROUTETHREE TRANSACTIONS · ONE HISTORICAL CASE
Follow the on-chain path
TWO SOURCE ACCOUNTS
2XHh…E6uK10M GFOF
7Hnq…jfPPY5M GFOF
Different recorded controllers
RECEIVING TOKEN ACCOUNT15M GFOFFYYi…B1WH
Transfers received. No sale shown yet.
EXECUTED SWAP ROUTE15M GFOF INMeteora DBC → USDC
226.961368 USDC was an intermediate leg.
SIGNER’S ACCOUNT2.611147511 wSOL OUTAJyE…YZRo
Unwrapped; native balance rose 2.588829226 SOL net.
01 / TRANSFER12:44 UTC
10 million GFOF moved in
Token account 2XHh…E6uK ↗ sent 10,000,000 GFOF to FYYi…B1WH ↗. This receipt shows a token transfer, without a payment back to the source account.
Check transaction · slot 421420932 ↗02 / TRANSFER13:41 UTC
5 million more arrived
A different token account, 7Hnq…jfPPY ↗, sent another 5,000,000 GFOF to FYYi…B1WH. Its recorded controller differs from the first source account’s controller. The receipts do not establish that those controllers are the same person.
Check transaction · slot 421429492 ↗03 / EXECUTED SWAP17:47 UTC
15 million GFOF swapped
The FYYi…B1WH controller signed a successful route sending 15,000,000 GFOF into the Meteora DBC pool. The route produced 226.961368 USDC as an intermediate leg, then delivered 2.611147511 wrapped SOL to a temporary account controlled by the signer. That account was closed into native SOL.
Check swap and route · slot 421466364 ↗WHAT THE RECEIPT SUPPORTSOBSERVED SWAP
Where the value landed
The final wrapped SOL went to an account controlled by signer AJyE…YZRo ↗ and was unwrapped in the same transaction. After referral payment and transaction costs, that signer’s native SOL balance rose by 2.588829226 SOL. The 226.961368 USDC was routed onward and must not be counted as additional final proceeds.
WHERE THE TRAIL STOPSNOT INFERRED
No person or profit claim
This case does not identify a beneficial owner, prove profit, establish a Jito bundle, or trace the SOL after this transaction. It does not classify every movement by these accounts or every GFOF sale. The current top-account rankings were captured months later and are not historical May rankings.
SOURCE & METHOD
Check all three receipts
A bounded public Solana RPC capture saved the finalized, parsed transactions. We compared the transfers and route with Solana Explorer. This case labels the first two events transfers and the third an executed swap because the transaction links GFOF input to the intermediate USDC leg and final SOL receipt. It is a dated teaching example, not an automatic tracker.
01 Three successful, finalized signatures
02 GFOF and quote-asset transfer instructions
03 Source signer’s before/after SOL balance
Read parsed source receipts (JSON) ↗02 / THE REPORT
EXAMPLE ONLYWhat a useful answer looks like
ILLUSTRATIVE ASSET
Sample Token
One fictional mint. One place to separate what the chain says from what people guess.
SUPPLY STRUCTUREILLUSTRATIVE
Where the supply sits
47%TOP 20 ACCOUNTS
Account A · unclassified18%
Account B · unclassified12%
Account C · unclassified9%
Accounts D–T · unclassified8%
TOKEN CONTROLSILLUSTRATIVE
Who can change it?
Mint authorityNone in example
Would indicate whether additional units can be minted at the captured slot.
Freeze authorityNone in example
Would indicate whether token accounts can be frozen under this program.
A missing authority is one fact, not a blanket safety verdict. Token-2022 extensions require their own review.
LAUNCH & COORDINATIONNOT CHECKED
Was it “bundled”?
A same-slot buy or shared funder can point to coordination. Neither alone proves common control or a Jito execution bundle.
Bundle verdictUnknown
This panel would link the exact transactions and rule behind any future finding. No accusation from a pattern alone.
03 / THE PROOF
Make the evidence inspectable
A real report would expose its RPC methods, raw account links, captured slot, source timestamp, classification rule and unresolved gaps. Readers should be able to challenge a finding.
01 On-chain observation
02 Explained inference
03 Unknowns & limits