Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTrack a company’s Solana treasury by maintaining a verified register of its public wallet addresses, watching those addresses for balance and flow changes, and then checking each material movement at the transaction-instruction level. A token leaving a wallet is not proof of a sale: confirmation requires the transaction’s token movements, destination or market context, and—when making an attribution claim—supporting company disclosure or other corroboration.
What you can—and cannot—learn from a Solana treasury
Solana makes public keys, token balances, transaction signatures, instructions, signers and fees visible on-chain. That transparency lets you measure what an address did, when it did it and which other addresses or programs it interacted with. It does not automatically reveal the legal owner, the person operating the wallet or the business purpose of a transfer.
As an Amazon Associate I earn from qualifying purchases.
A company may use several kinds of accounts at once: an operating wallet for routine payments, a custody wallet, a staking account, an exchange deposit address, a contract-controlled account or temporary addresses created for a particular transaction. Exchanges may also use omnibus wallets that hold assets for many customers. Consequently, wallet monitoring is an evidence process, not a shortcut to proving corporate ownership or intent.
The practical objective is to separate three layers of confidence:
#1 Best Overall
- Observed fact: a specific address sent or received a specified token in a transaction identified by a signature.
- Attribution: evidence indicates that the address is used by, or associated with, the company.
- Intent: the transaction is consistent with a sale, internal rebalance, staking action, financing movement or another purpose.
Keep those layers separate in notes and published analysis. “The address transferred 250,000 tokens to an address that interacted with a decentralized-exchange program” is an on-chain observation. “The company sold 250,000 tokens” is a stronger conclusion that needs attribution and intent evidence beyond the transfer itself.
Step 1: Build and verify the company’s address register
The hardest part of treasury tracking is usually identifying every relevant address. Begin with addresses the company has disclosed in treasury announcements, audited filings, token-holder materials or a prior transaction that can be independently verified. Record the evidence for each association instead of treating a label or a single transfer as proof.
Fields to record for every address
| Field | What to capture | Why it matters |
|---|---|---|
| Public key | The complete Solana address, copied exactly | Prevents analysis of a truncated or mistyped address |
| Working label | Operating wallet, custody wallet, staking account, exchange deposit, contract-controlled account or unknown | Separates unlike activity and makes later review clearer |
| Association evidence | Company disclosure, filing, signed message, verified prior transaction or other documented basis | Shows why the address is included |
| Date first observed | The date you first saw the address used in the company context | Defines the beginning of your monitoring window |
| Confidence and notes | High, medium or low confidence, plus the supporting transaction signatures or documents | Stops tentative clues from being presented as established ownership |
How to test an address before adding it
- Open the address in a Solana block explorer and check its historical activity, token holdings and counterparties.
- Look for a transaction that ties the address to a disclosed company wallet, treasury movement or signed announcement.
- Check whether the observed activity fits the proposed role. A staking account will show staking-related behavior; an exchange deposit may show rapid consolidation into an exchange-controlled address.
- Search for evidence of a different owner. A label supplied by a third party can be incomplete or wrong, and an address may have changed hands.
- Write down the reason for inclusion and the date of the check. If the only clue is one inbound transfer, mark the association as unverified rather than treating it as company-controlled.
Companies can rotate addresses, split custody among providers or move assets through temporary accounts. Revisit the register whenever a known wallet sends funds to a new address, a filing identifies a new custodian or a recurring pattern appears that cannot be explained by the existing set.
Recommended Free Tools
Step 2: Put the addresses on a watchlist
Solscan describes itself as a Solana block explorer for searching accounts, transactions, tokens and programs. Its Wallet feature lets a user keep up to 10 wallets under one account’s watchlist. That limit is suitable for a small treasury set; larger address groups need a spreadsheet, API process or data platform in addition to the browser watchlist.
Recommended watchlist setup
- Create one watchlist entry for each verified public key, using a label that identifies the company and the wallet’s working role.
- Keep the full address in your own register even when the interface displays a shortened form.
- Note the date and time when each address was added and the evidence supporting the label.
- Set a review cadence. Daily checks suit a treasury that moves frequently; weekly or monthly checks may be enough for a dormant reserve, provided alerts or a separate process cover material movements.
Use the watchlist as an observation tool, not as an ownership registry. A displayed label or a wallet’s position in your list does not change the evidentiary status of the underlying address.
Step 3: Read treasury balances and flow analytics
On an account page, open the Analytics view to move beyond a single current balance. Solscan documents charts for transfer count, active age, unique active days, longest activity streak, daily USD balance, daily value transferred in and out, and top inflow and outflow addresses. The transfer heatmap shows which days were active, with selectable windows of seven days, one month or three months. The visualizations are generated from indexed on-chain records and refreshed periodically, so treat them as a monitoring view and verify important events against the underlying transactions.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Signals worth monitoring
- Balance drawdown: a sharp decline in token quantity or USD value can indicate a sale, transfer to custody, staking, collateralization or another treasury action.
- Repeated operating flows: regular transfers to the same counterparties may reflect payroll, vendors, market-making or internal treasury operations.
- New counterparties: a previously unseen destination deserves transaction-level review, especially if it receives a large share of the balance.
- Activity concentration: a heatmap cluster can show a liquidation window, a funding campaign or a routine batch process, but it cannot identify the purpose on its own.
- Inflow and outflow asymmetry: large inflows followed by rapid outflows may represent exchange settlement or internal routing rather than net selling.
How to review a suspected drawdown
- Choose the relevant analytics window and record the starting and ending balance, the displayed currency and the date you viewed it.
- Identify the days on which the balance changed materially.
- Open the transfer list for those dates and group movements by token mint and destination.
- Compare the total outflow with inflows, staking changes and transfers among addresses already in your register.
- Mark events for transaction-level inspection; do not label a sale from the chart alone.
USD charts are useful for trend context but can change with the price source and the time at which the chart was refreshed. Preserve the token quantity, mint and transaction signature as the primary evidence.
Step 4: Preserve each material movement at transaction level
For every movement that could affect a treasury conclusion, open the blockchain or account transaction view and save a structured record. Solscan’s transaction view exposes signatures, blocks or slots, times, instructions, signers and fees. Token movements and decoded instruction details provide the additional information needed to classify what happened.
Minimum transaction record
| Item | Record | Use in analysis |
|---|---|---|
| Signature | The complete transaction signature | Stable reference for auditing and later retrieval |
| Slot or block and timestamp | The chain position and displayed time, with your capture time | Orders events and preserves the time window |
| Signer and fee payer | Accounts that authorized or paid for the transaction | Helps distinguish an account’s own action from a program-mediated movement |
| Instructions | Program calls and decoded actions | Shows whether the transaction involved a transfer, swap, staking action or another operation |
| Token mint and amount | Exact mint address, quantity and decimals | Avoids confusing similarly named tokens |
| Source and destination accounts | Every relevant token account and recipient | Reveals routing, internal transfers and final recipients |
| Fee and balance changes | Network fee and native-token changes | Supports reconciliation and detects failed or partial-looking interpretations |
Save the signature, a screenshot or archived page where appropriate, and a row in your working file. A chart can change as indexing is refreshed; the signature is the durable audit reference.
Step 5: Decide whether a token movement was a sale
A token outflow alone does not establish a sale. It may be an internal rebalance, movement to a custodian, staking operation, bridge transfer, treasury financing, payment or a transfer to an exchange without an immediate sale. Classification requires the complete transaction and its surrounding context.
Transaction-level sale checks
- Identify the token movement. Confirm the exact mint, quantity, source token account and destination account. Check whether several token movements occur in the same transaction.
- Read the decoded instructions. Determine whether the wallet interacted with a decentralized-exchange program, market address, routing program or only with a system or token program.
- Find the asset received. A swap normally produces an incoming asset or native SOL, less fees and any protocol charges. An outbound transfer with no corresponding consideration is not, by itself, a swap.
- Check amounts and timing. Compare the outgoing and incoming quantities and note whether the transaction contains multiple hops, liquidity-pool legs or aggregator routing.
- Inspect the counterparty. A recognized program or market address can support a “swap routed through” description. An ordinary wallet address requires more caution because it may be a custodian, market maker, affiliate or another company-controlled address.
- Apply an evidence label. Use “outbound transfer,” “swap routed through [program],” or “transaction consistent with a sale” unless a company disclosure or additional corroboration supports the stronger statement that the company sold the tokens.
Solscan’s FAQ says this information can be checked using program addresses or market addresses. Token pages can add holder, price, pair, liquidity, volume and recent-transaction context. Those fields help explain a swap, but they do not independently prove who controlled the receiving address or why the company acted.
Free tools Windows power users keep installed
One-click scans. No signup required.
Common patterns and cautious interpretations
| Observed pattern | Reasonable description | What remains unproven |
|---|---|---|
| Tokens move to another address in the same company register | Internal treasury transfer or rebalance | Whether the destination is legally controlled by the same entity |
| Tokens move to a known DEX or market program and another asset arrives | Swap routed through that program; potentially consistent with a sale | Business intent, accounting treatment and beneficial ownership of every pool participant |
| Tokens move to an exchange deposit address | Transfer to an exchange or custody venue | Whether and when the tokens were sold |
| Tokens move to a staking or validator-related account | Possible staking operation | Whether the company later liquidated rewards |
| Tokens leave with no apparent consideration | Outbound transfer requiring investigation | Sale, donation, payment or internal purpose |
Step 6: Export history and reconcile the treasury
CSV exports turn browser observations into an auditable working file. Solscan documents exports from account-transfer and token-holder views. Its export documentation states that the supported data can be tracked only from 2021-07-07 onward. If you need earlier activity, use another data source or state clearly that the historical record begins on that date.
Export procedure
- Choose the exact account and token or transfer view you are studying.
- Set a fixed date range and record the range, timezone shown by the interface and export date.
- Download the CSV without modifying the original file.
- Create a working copy with columns for transaction signature, timestamp, mint, amount, direction, source, destination, program, classification and review status.
- Link every manually reviewed event to its signature and keep notes for uncertain classifications.
Balance reconciliation formula
For each token mint, calculate:
Opening balance + inflows − outflows + or − other balance changes = closing balance.
Use token quantities rather than USD values for the reconciliation. Investigate differences caused by staking rewards, token-account closures, decimal conversion, a date-range boundary, failed transactions or activity outside the export’s coverage. Keep the original CSV, the cleaned working file and a dated record of any adjustments.
Step 7: Cluster related wallets without overstating ownership
Solscan’s Data Intelligence features combine indexed and parsed on-chain data with labels for tokens, programs, accounts and funding relationships. Funded By tooling examines first-recorded funding relationships, and the API documentation describes single-account or batch tracing for up to 50 accounts per request. These tools can reveal common funders, exchange-deposit patterns or wallet-generation relationships.
How to use funding relationships
- Run the funding trace for a known address and record the first funding transaction, funder address and date.
- Compare that funder with the first funders of other candidate addresses.
- Look for repeated operational behavior, shared program interactions and synchronized transfers.
- Classify the relationship as a clue—such as “same apparent funder” or “common exchange route”—rather than as proof of a shared legal owner.
- Seek independent corroboration in company disclosures, signed messages or consistent long-term behavior before merging addresses into one treasury total.
A common funder can be an exchange, service provider, employee, custodian or automated wallet-generation system. Conversely, one company can use several unrelated funders. Wallet clustering improves discovery; it does not establish control or management intent.
Choosing a monitoring method
The right method depends on how many addresses you follow and how defensible the record must be. A manual explorer workflow is usually fastest for a small number of wallets. A repeatable export or API process becomes more valuable when you need regular reconciliation, historical comparisons or review by another person.
| Method | Best for | Strength | Trade-off |
|---|---|---|---|
| Explorer watchlist and account pages | A few wallets and occasional checks | Fast visual review of balances, counterparties and activity | Manual, limited watchlist capacity and greater risk of inconsistent notes |
| CSV export and spreadsheet | Periodic reporting and reconciliation | Creates a portable, reviewable working file | Requires cleaning, classification and awareness of the 2021-07-07 coverage boundary |
| API or scripted workflow | Many wallets, recurring checks and alerts | Repeatable collection and batch processing; funded-by tracing supports up to 50 accounts per request | Requires technical setup, data validation and ongoing maintenance |
| Data-intelligence and label views | Address discovery and relationship analysis | Surfaces program, account and funding clues | Labels and relationships are not legal-ownership proof |
Build an evidence file that survives review
For every reporting period, preserve the scope and method alongside the data. State the company or treasury definition, included addresses, excluded addresses, token mints, date range, timezone, valuation convention and the date you captured the information.
Rank #4
Evidence-file checklist
- Address register with source of attribution and confidence level.
- Watchlist or monitoring snapshot showing the addresses covered.
- Original CSV exports and a read-only copy of any archived pages or screenshots.
- Transaction signatures for every material inflow and outflow.
- Decoded instruction notes identifying programs, markets and counterparties.
- Reconciliation showing opening balance, movements and closing balance per token.
- A classification field that distinguishes observed transfer, probable internal movement, swap evidence and unresolved event.
- A timestamp for each review and the analyst’s assumptions.
This separation is particularly important when publishing a figure such as “treasury sold tokens.” A defensible statement should identify the addresses reviewed, the time window, the signatures supporting the classification and the evidence connecting those addresses to the company.
Failure modes and how to correct them
Following only one wallet
Problem: The company may have moved assets to custody, staking or exchange addresses that are not in the initial list.
Correction: Start with disclosed addresses, then review material destinations and update the register with documented confidence levels.
Treating a label as ownership proof
Problem: Explorer labels can be incomplete, stale or incorrect.
Correction: Preserve the label as a clue, but require disclosure, signed evidence or a consistent transaction history for stronger attribution.
Calling every outflow a sale
Problem: Transfers can represent rebalancing, staking, financing, payment or exchange deposits.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Correction: Inspect decoded instructions, incoming assets and program or market context; use a qualified description when consideration is not visible.
Relying on USD charts for accounting
Problem: USD values vary with price data and chart refresh timing.
Correction: Reconcile exact token quantities and retain the mint address, then use USD only as contextual information.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Assuming an export covers all history
Problem: Solscan documents export coverage from 2021-07-07 onward.
Correction: Mark that boundary in the report and obtain another source for older activity rather than implying a complete historical series.
A practical monitoring cadence
Daily or event-driven review
Use this cadence when the treasury is actively trading, a disclosure is imminent or a large balance is at risk. Review new transactions, flag material token movements and preserve signatures immediately.
Weekly review
Compare balances with the prior week, inspect new counterparties and update the address register for newly funded or newly active accounts. Export the period if you need a repeatable record.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Monthly or quarterly reporting
Run a full reconciliation by token, review staking and custody movements, refresh address-attribution evidence and document the precise coverage window. Separate market-price changes from quantity changes so a valuation decline is not mistaken for a sale.
Bottom line for interpreting a company’s Solana wallets
A reliable tracker combines a verified address register, watchlist monitoring, account analytics, transaction-level inspection, CSV reconciliation and cautious wallet clustering. The blockchain can show exactly what a public address did; it cannot, by itself, guarantee who legally controlled that address or why the transaction occurred. Report signatures, mints, amounts, counterparties and time windows, and reserve the word “sale” for transactions whose swap evidence and attribution support that conclusion.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
