A CPA managing client portfolios that include Solana assets faces a recurring practical problem: tax documentation requires precise transaction histories, cost bases, and holdings snapshots, but blockchain data exists across thousands of addresses and is often scattered across exchange exports, wallet backups, and incomplete records. Reconstructing the full audit trail for tax year-end reporting or IRS substantiation demands a reliable source that aggregates on-chain data accurately and allows systematic review without relying on exchange platforms that may have limited historical access or have ceased operations.
Solscan, the official blockchain explorer for the Solana network, provides a direct window into immutable transaction records and wallet states without requiring clients to grant access to private keys or exchange accounts. For accountants and tax professionals, this matters because it separates data retrieval from custody and trading platforms, reducing dependency on third-party record-keeping and creating an independent verification layer. The tool’s wallet explorer, transaction history features, and block-level data transparency enable systematic reconstruction of Solana holdings, cost basis tracking, and realized gains or losses with minimal manual entry and maximum audit defensibility.

Why accountants need Solscan rather than exchange statements alone
Exchange platforms provide internal ledgers but they do not reflect the complete Solana transaction universe. A client may have moved tokens off an exchange to a self-custodied wallet, traded on a decentralized exchange, received token transfers from employers or protocols, or interacted with smart contracts in ways that generate unrealized income. The exchange’s export covers only activity on that platform, leaving gaps that can trigger audit adjustments if discovered later.
Solscan’s approach is fundamentally different. Every transaction that touches the Solana blockchain—whether it occurs on an exchange, through a wallet application, or via a decentralized protocol—is recorded in the immutable ledger and accessible through the explorer’s search interface. For a wallet address, the entire history is retrievable and includes timestamps, fee amounts, sender and recipient addresses, token transfers, and confirmation status. That transparency means an accountant can independently verify whether a client’s reported transactions match on-chain reality.
The practical advantage is audit defensibility. When the IRS or a tax authority questions a transaction, the accountant can point to the Solana blockchain record via Solscan, which shows consensus-verified data rather than relying on an exchange’s internal database or a client’s unsupported explanation. The blockchain record does not lie about when a transaction occurred, how much SOL was transferred, or what fees were paid. Those facts can be verified months or years later using the same tool, which is not the case with exchange databases that may have been pruned, sold, or shut down.
Additionally, solscan requires no login, no private key upload, and no client authentication. An accountant can examine any public wallet address without the client needing to log into their exchange account or share sensitive credentials. This separation of concerns improves both security and workflow efficiency, because sensitive access is never shared for record-keeping purposes.
Using the wallet explorer to document holdings and cost basis
The wallet explorer in Solscan is designed to answer a simple question: what does a given address own, and when did that ownership state change? When an accountant enters a client’s Solana wallet address, the interface displays all tokens held at that address, with quantity, current price data, and total USD value. For a client with 100 SOL and 50,000 USDC in a self-custodied wallet, Solscan will show both balances instantly and can timestamp that snapshot for year-end reporting.
More critically, the wallet balance view includes transaction history linked to that address. Every inbound transfer, outbound transfer, token swap, and interaction with smart contracts is listed chronologically with exact timestamps and transaction signatures. An accountant can export or manually review this history to reconstruct the cost basis of holdings. If a client purchased 10 SOL on June 15 at $22 per SOL and 15 SOL on December 1 at $180 per SOL, the wallet explorer will show both transactions with the date and the receiving address, allowing the accountant to assign the correct cost to each lot.
The timestamp precision is especially valuable. Solana’s block times are approximately 400 milliseconds, meaning the explorer shows transaction timing to the second or better. For tax purposes, this eliminates ambiguity about whether a transaction occurred before or after a price-sensitive event, whether a holding period threshold was met, or whether a wash-sale rule might apply. An accountant can click on any transaction to see the full details, including the sender, recipient, amount, and network fee paid, all of which feed into basis calculations.
For tokens with significant price volatility, this precision becomes essential. A token received on March 10 at 9:15 AM UTC versus 5:47 PM UTC could represent a meaningful difference in fair market value if the price moved sharply that day. Solscan provides the exact timestamp and, through its token overview feature, allows accountants to look up historical price data (either through external pricing APIs or manual cross-reference with exchanges and market-data providers) to assign the correct fair market value at the time of receipt.
Reconstructing realized gains and transaction fees
When a client sells tokens or executes a swap, two items must be documented for tax reporting: the proceeds received and the cost basis of the tokens disposed. Solscan’s transaction history makes both available. When an accountant finds a transaction in which tokens were sent to a decentralized exchange or swap contract, the explorer will show the outbound token amount, the receiving contract address, and the transaction hash. Cross-referencing with the next transaction from that address or looking at the contract interaction details reveals the token received in return, its amount, and the value at execution.
Network fees are equally important but often overlooked. Solana transactions carry a base fee of 5,000 lamports (approximately 0.00025 SOL at typical network conditions) per signature, plus variable compute fees depending on the transaction complexity. Solscan displays the total fee paid for every transaction. Under U.S. tax code, transaction fees are typically deductible as a cost of producing income or, for self-employed traders, as a business expense. An accountant must capture these fees per transaction and sum them for the year to reflect the true cost of trading activity.
The wallet explorer approach also catches transactions that might otherwise be missed. If a client received an airdrop, staking reward, or protocol distribution, Solscan will show the transfer with the sending address clearly labeled. An accountant can then verify whether the transfer came from an official protocol contract and research the fair market value at receipt to calculate taxable income. Airdrops and rewards are often omitted from exchange records if the client never moved them to a trading platform, making the independent blockchain record essential for completeness.
For complex multi-leg transactions—such as a swap that involves three token hops or a deposit into a yield protocol followed by a withdrawal—Solscan’s block explorer feature allows the accountant to examine the entire atomic sequence. Each step is visible, timestamped, and attributable to specific contract addresses, which makes it possible to trace the flow of value accurately rather than relying on a client’s recollection or an exchange’s abbreviated summary.
Token and NFT data for comprehensive asset documentation
Solscan includes a token overview section that displays supply, circulation, contract information, and trading history for any token on the Solana network. For accountants tracking obscure or recently created tokens in client portfolios, this feature provides a way to verify that a token actually exists on-chain, understand its supply dynamics, and confirm the contract address to ensure the client is not holding a counterfeit or scam token.
NFTs present a distinct reporting challenge because they do not fit neatly into token quantity-based tracking. Solscan’s NFT analytics feature allows accountants to search for a specific NFT collection or individual token ID, review transaction history, and confirm ownership at any point in time. If a client claims to own an NFT but the wallet address does not currently hold it, Solscan will show when it was transferred out, to which address, and the timestamp. This creates an audit trail that clarifies whether the asset was sold, gifted, lost, or stolen, each of which has different tax implications.
For NFTs with marketplace sales, the transaction history on Solscan shows the sale price and the receiving address of the buyer, allowing the accountant to confirm the realized gain or loss. Because NFT prices are often volatile and uniquely determined by each sale, Solscan’s block-level transaction data is superior to relying on marketplace screenshots, which can be edited or deleted if the marketplace undergoes outages or delistings.
Developer tools and API access for large-scale reporting
Accountants managing multiple client addresses or conducting portfolio audits can use Solscan’s API to automate data retrieval. The API provides programmatic access to wallet balances, transaction histories, token metadata, and block data. For firms handling dozens of clients with Solana holdings, writing a script to pull transaction data directly into a spreadsheet or accounting software is far more efficient than manually querying addresses one by one.
The API is free to use within reasonable rate limits and does not require the accountant to hold Solana tokens or pay per query. This makes it accessible to accounting practices of any size. A CPA firm can integrate Solscan data directly into their existing tax-preparation workflow, using the API to automatically populate transaction logs, cost basis tables, and realized gains schedules. This reduces manual data entry, decreases transcription errors, and speeds up year-end reporting.
For more sophisticated analysis, the developer tools also include smart contract verification, which allows accountants to inspect the code of protocols a client interacted with. While most accountants will not audit contract code themselves, they can confirm that a contract has been verified by its developers and published on Solscan, which provides some assurance that the protocol is not an obvious scam. This is particularly useful when clients claim to have earned yield or fees from novel protocols—the accountant can cross-check the contract address and transaction history to assess the credibility of the income claim.
Handling privacy, staking, and wrapped tokens
Solscan shows all public Solana blockchain activity by design; it does not obscure transaction details or amounts. This transparency is essential for tax reporting but means accountants must educate clients about privacy expectations. Any wallet address that a client reveals to an accountant becomes visible in Solscan’s search history, and the accountant should clarify that the blockchain ledger is permanently public. For clients concerned about privacy, the accounting process must balance that concern against the compliance requirement to document transactions accurately.
Staking rewards represent another reporting nuance. When a client delegates SOL to a validator and receives staking rewards, the rewards appear as transfers into the client’s wallet. Solscan will show the timestamp and amount of each reward, which the accountant must classify as taxable income at fair market value on the date received. The wallet explorer makes it easy to identify all staking-related transactions by filtering for transfers from known validator or staking pool contract addresses, though accountants should verify the specific contract addresses because scam contracts sometimes mimic legitimate ones.
Wrapped tokens—such as wrapped Bitcoin (WBTC) or wrapped Ether (WETH) on Solana—require careful tracking because they represent claims on assets held elsewhere. If a client holds WBTC on Solana, the fair market value should reflect Bitcoin’s price, not a Solana-specific token price. Solscan will correctly label the token and link to its metadata, but the accountant must ensure pricing data is sourced from the underlying asset market, not exclusively from Solana DEX trading data.
Audit trail and compliance documentation best practices
An effective Solana tax audit should include a Solscan-based documentation package: wallet address searches showing the client’s holdings at year-end, a chronological transaction list exported or printed from Solscan, token acquisition and disposal records with timestamps and fair market values, and a summary of all network fees paid. This package, combined with the client’s exchange statements and proof of purchase (if available), creates a defensible record that ties together on-chain facts with tax calculations.
Accountants should also document the process used to identify all relevant wallet addresses. A client may control multiple self-custodied wallets, which means a single address on Solscan will not capture the entire portfolio. A systematic interview or reconciliation process—asking the client to list all Solana addresses they control and comparing that list to actual holdings—is essential to avoid omitting assets. Solscan cannot know which addresses belong to a client unless the accountant knows to ask, and omitting addresses is a common cause of audit adjustments.
For transactions involving decentralized protocols, staking, or yield farming, the accountant should create a supplemental schedule that maps each interaction to its tax character. A deposit into a liquidity pool, for example, might not generate an immediate taxable event (depending on the transaction structure), but withdrawal and any fees or income received would. By using Solscan to trace the complete lifecycle of such transactions, the accountant can provide detailed documentation rather than a generic description that may not satisfy auditors.
Record retention is critical. Solscan’s data is permanent because it reflects the immutable Solana blockchain, but blockchain explorers and websites can change, disappear, or modify their interfaces. Accountants should consider creating PDF exports or screenshots of key Solscan pages as part of their working papers, alongside the original blockchain transaction hashes, which can be independently verified against any other Solana explorer in perpetuity.
Limitations and complementary tools
Solscan shows what happened on the Solana blockchain but not why. If a transaction lacks clear labeling—such as a transfer to an unknown contract address—Solscan alone cannot explain whether it was a deposit, swap, or loss. An accountant may need to cross-reference the transaction hash with external sources, such as DEX transaction trackers, staking pool records, or direct client communication, to classify the transaction correctly for tax purposes.
Pricing data is another limitation. Solscan provides current token prices but limited historical price data. For transactions from months or years ago, the accountant must source fair market values from external price feeds, exchanges, or historical data providers such as CoinGecko or Messari. This is not a limitation of Solscan itself but a necessary step in the broader tax-reporting workflow.
Finally, Solscan is a Solana-specific tool. Clients with multi-chain portfolios will need additional explorers such as Etherscan for Ethereum, or will need to use cross-chain portfolio trackers that integrate multiple blockchains. For practices serving clients with only Solana holdings or with Solana as the dominant asset class, Solscan is sufficient and often preferable to generic portfolio trackers that may be less detailed for Solana’s specific transaction types and token standards.
Frequently asked questions
Can I use Solscan to verify a client’s cost basis without accessing their exchange account?
Yes. Solscan’s wallet explorer will show every on-chain transaction tied to a client’s self-custodied Solana address, including purchases, transfers, and receipts. The blockchain record provides timestamps, amounts, and recipient details. However, if the client also trades on exchanges or through wallet applications that do not post transactions to the chain immediately, you will need to cross-reference with exchange statements for a complete picture. The wallet explorer captures self-custodied and finalized transactions; it does not see pending orders or internal exchange transfers that have not yet been settled on-chain.
How do I handle fair market value for tokens with low liquidity or historical price data gaps?
Solscan will show you the token’s metadata and current price, but for historical valuations, you must use external sources such as CoinGecko, Messari, or exchange trading history from the date of the transaction. For very obscure tokens with no liquid market history, you may need to use a reasonable valuation method (such as the lowest recent price or an appraisal if the token has utility) and document the method you chose. The IRS expects reasonable effort in good faith; Solscan’s transaction data alone does not determine value, but it does establish the date and quantity that must be valued.
What is the best way to document staking rewards using Solscan?
Search for your client’s wallet address on Solscan and filter the transaction history for transfers from known staking pool or validator contract addresses. Each reward transfer will show a timestamp and amount. Export or manually log these transactions, then assign fair market value to each based on SOL’s price on the receipt date. Solscan will not label every transaction as a “staking reward,” so you may need to cross-reference the sending contract address with the staking pool operator to confirm the transaction’s nature. Document this confirmation in your working papers to support the income classification.