Node operators and blockchain researchers managing infrastructure on the Solana network face a recurring practical challenge: distinguishing healthy validator performance from degradation, understanding network congestion patterns, and identifying when a validator has fallen out of consensus or missed critical epochs. The tools available determine whether this monitoring remains reactive—discovering problems after they affect production—or proactive, allowing operators to spot issues before they cascade into missed slot assignments or stake withdrawal penalties.
Solscan serves as the primary gateway for this real-time visibility. As a block explorer purpose-built for the Solana network, it provides detailed epoch data, validator rankings, historical performance metrics, and transaction-level confirmation statistics that together form a complete picture of network health. For operators running their own nodes, understanding how to interpret Solscan’s validator dashboards and epoch data becomes essential to optimizing hardware allocation, identifying network bottlenecks, and making informed decisions about stake delegation.
Understanding Solscan’s validator monitoring interface
The validator section of Solscan displays a ranked list of active validators on the Solana network, ordered by stake, skip rate, and other performance indicators. Each validator entry shows current stake amount, the number of nodes operated by that entity, and historical commission rates. This information is drawn directly from on-chain accounts and updated in real time as stake moves and validator configurations change.
For a node operator examining their own validator, the first useful metric is skip rate: the percentage of assigned slots the validator failed to produce a block for during the current and recent epochs. A skip rate approaching zero indicates reliable block production; rates above 5 percent suggest hardware constraints, network connectivity issues, or software problems. Solscan reports this for each validator separately, making it immediately clear whether performance degradation is isolated to one operator or systemic across the network.
Commission rate, displayed prominently in the validator list, represents the percentage of staking rewards that the operator retains before distributing the remainder to delegators. Operators reviewing competitors often use Solscan to track commission movements; a sudden increase may signal financial pressure or infrastructure changes, while decreases typically appear during competition for stake. The historical data available through solscan allows operators to observe seasonal or trend-based shifts in the validator landscape.
Stake concentration is another critical observation point. Solscan makes it easy to see how much stake is delegated to the top 20 or 50 validators, which directly relates to network decentralization. A healthy network typically shows more evenly distributed stake; concentration above 33 percent in the largest operators raises concerns about consensus vulnerability. Operators using Solscan to benchmark their own position often ask whether their stake rank is moving in the right direction relative to overall network growth and whether commission adjustments are attracting or losing delegation over time.
Tracking epoch transitions and network epochs
The Solana network operates in discrete epochs, each lasting approximately two days. During each epoch, validators are assigned slots to propose blocks, and their performance is measured and recorded on chain. Solscan’s epoch page provides a live countdown to the next epoch boundary, the current slot within the active epoch, and historical data on every completed epoch for many months into the past.
The epoch view displays aggregate network statistics: total active stake, number of validators, average skip rate, and network inflation data. These metrics answer important structural questions. A declining number of active validators combined with rising concentration in the top performers may indicate that smaller operators are exiting due to economic pressure or hardware costs. Rising skip rates across the network could signal increased traffic, validator hardware strain, or temporary network issues. Solscan’s historical epoch data lets operators distinguish between temporary fluctuations and sustained trends.
Within each epoch, validators must produce blocks during their assigned slots. Solscan breaks down slot production by validator, showing which operators claimed specific slots and whether they successfully produced blocks. A validator assigned to 100 slots who produces only 95 has a 95 percent success rate for that epoch; Solscan displays this alongside network averages, making it easy to judge whether a validator is performing better or worse than the median. Over a full epoch, this becomes the definitive skip rate figure that affects staking rewards distribution.
Network epochs also serve as the boundary for stake account updates and delegation changes. When you delegate stake to a validator or request an undelegation, the change takes effect at the start of the next epoch. Solscan’s epoch countdown is therefore practical information for anyone managing stake: if you see the epoch ending in 18 hours and you need delegation to take effect for tomorrow’s rewards, you must complete the transaction before the epoch boundary. The explorer’s real-time updates make this planning possible without consulting multiple data sources.
Analyzing block production and transaction confirmation patterns
Beyond the high-level validator rankings, Solscan provides block-by-block detail. Each block produced on Solana carries metadata: the proposing validator, the number of transactions included, the network fee paid per transaction, and the confirmation status. For a developer or operator concerned about transaction finality, this information directly answers whether transactions are being confirmed quickly or experiencing delays.
Transaction confirmation on Solana nominally occurs once a block is finalized; however, block production is not uniform. During periods of high network load or when major validators are offline, block times can extend beyond the typical 400-millisecond average. Solscan’s real-time block view shows actual block arrival times and allows filtering by validator. An operator suspecting network congestion can search for blocks from a specific time range and immediately see whether slot times were stretched or block production was interrupted.
The transaction search function on Solscan provides signature-level detail: exact fee paid, accounts accessed, program invocations, and token transfers. When investigating a failed or slow transaction, an operator can paste the transaction signature and see precisely where it landed in a block, which validator produced it, and whether any instruction failed. This level of forensic detail is essential for debugging smart contract interactions or understanding why a particular token transfer took longer than expected.
Fee trends are also visible through Solscan’s transaction history. By scrolling through recent blocks, an operator can observe whether the network is in a high-fee or low-fee regime. During periods of competition for block space (though rare on Solana compared to other chains), users bid with higher fees, and Solscan’s data makes this visible immediately. This information influences decisions about when to submit time-sensitive transactions and whether infrastructure costs are likely to rise due to network congestion.
Using Solscan’s API and advanced filtering for node operators
The read-only API exposed by Solscan enables programmatic access to the same data visible through the web interface. Node operators monitoring their infrastructure can integrate Solscan API calls into automated alerting systems. When a validator’s skip rate exceeds a threshold within an epoch, when assigned slots are missed consecutively, or when delegation below a target level is detected, an alert can trigger automatically rather than requiring manual monitoring.
Advanced filtering on Solscan allows operators to construct complex queries: show all blocks produced by a specific validator during a certain time range, filter transactions by program, or track NFT activity on a particular collection. For operators investigating performance issues, filtering blocks by their validator and examining the transaction load in those blocks can reveal whether the issue is external network congestion or a sign of hardware overload on the validator itself.
The API also supports historical queries, allowing retrospective analysis. An operator concerned about whether their validator has experienced a persistent performance decline can query Solscan’s data for the past 10 epochs, graph skip rates over time, and identify the exact moment when performance degraded. This historical perspective is crucial for correlating performance changes with infrastructure upgrades, software updates, or external events.
For developers building applications that depend on network health, Solscan’s data can inform decisions about validator selection for RPC calls. If an application queries a validator running high skip rates, transaction confirmations may be delayed. By consulting Solscan’s live validator metrics before routing traffic, applications can preferentially use high-performing validators and improve user experience. This represents an indirect but important use of the explorer: as a source of truth for network quality metrics that guide other infrastructure decisions.
Identifying network health issues through Solscan metrics
A systemic network issue typically manifests as a coordinated change in Solscan metrics. If skip rates across multiple large validators spike simultaneously, the problem is likely network-wide rather than specific to one operator. If only a few validators show degradation, the issue may be their infrastructure, ISP connectivity, or software version. Solscan’s aggregated view makes these distinctions visible at a glance.
Network epochs also serve as natural boundaries for diagnosis. If a validator had high skip rates in epoch N but normal performance in epoch N+1, the issue was likely transient. If degradation persists across multiple consecutive epochs, there is a systemic problem requiring investigation. Some operators use Solscan’s historical data to build trend analyses: comparing skip rates over 20 epochs reveals whether a validator is improving, declining, or stable.
Slot leadership itself is another data point visible through Solscan. Validators who consistently receive slot assignments but fail to produce blocks may be experiencing Byzantine behavior (intentionally skipping or producing invalid blocks) or severe hardware constraints. Solscan’s per-slot detail makes this visible: if a validator is assigned 100 slots and produces fewer than 50 blocks in an epoch, something is seriously wrong.
Fee dynamics also indicate network stress. When transaction fees spike in Solscan’s real-time data, it often precedes visible performance issues. High fees mean high demand, which can strain validator resources. An alert-conscious operator monitoring Solscan’s transaction feeds can preempt problems by scaling resources or adjusting configuration before actual service degradation occurs.
Delegators using Solscan to evaluate validator stake
Users deciding where to delegate stake face a choice among hundreds of validators. Solscan provides the data needed to make an informed decision. Before delegating, a potential delegator should review: the validator’s historical skip rate (lower is better), commission rate, and current stake (higher stake generally means better infrastructure but also more competition for rewards). Solscan displays all three pieces of information on one page, with filters to sort by any metric.
A validator with a 95 percent slot production rate over the past 10 epochs is demonstrably more reliable than one at 85 percent. Over a year, that 10 percent performance difference translates directly into compounding reward differences. Solscan’s historical data allows delegators to verify consistency: a validator that was reliable three months ago but is now frequently missing slots deserves scrutiny. This due diligence directly impacts staking yield.
Commission changes are also tracked through Solscan. Some validators run promotions with reduced commissions to attract stake, then increase them later. By reviewing Solscan’s historical commission data, a delegator can see the full pattern and make a more cautious decision about validators with volatile commission histories. A validator maintaining a stable, moderate commission typically signals a more professional long-term operation than one with erratic rate changes.
The validator’s self-reported information—name, website, geographic location—visible on Solscan can be cross-checked against public sources to identify professional operators. Some validators are clearly managed by established infrastructure providers; others are anonymous. For delegators concerned about validator continuity and professionalism, this information visible through Solscan is an important filtering step.
Practical workflow: Diagnosing a validator issue in real time
An operator notices their validator has not produced blocks in the past 15 minutes. The first step is to open Solscan and search for the validator by its identity or stake account address. Checking the most recent epochs, the operator can immediately see whether skip rate has spiked. If it has, the problem is confirmed as real and not a local node reporting issue. If the skip rate appears normal but recent blocks are missing, the issue may be in the node’s local block production chain or a very recent network partition.
Next, the operator checks the current network state. If other validators are also showing elevated skip rates, the issue is likely network-wide: a consensus failure, a mass client bug, or a temporary partition. In this case, the operator should review Solscan’s recent block stream for patterns and check whether Solana’s status page or community channels report known issues. If Solscan shows normal skip rates across the validator set, the problem is isolated to this operator’s infrastructure.
The operator then examines which slots were assigned to their validator in the current and previous epochs on Solscan. Were they assigned slots at all? If not, this explains zero production: the validator is not being asked to produce blocks. If slots were assigned but not claimed, the issue is validator uptime. The operator can now investigate local hardware, network connectivity, and validator software logs. Solscan’s data confirms the problem is real and bounds the diagnosis space, saving time on otherwise speculative troubleshooting.
Throughout this workflow, Solscan serves as the external source of truth. When an operator’s local tools report something different from Solscan, it signals a mismatch between what the node thinks is happening and what the network actually recorded. This distinction is invaluable for debugging: a local ledger out of sync looks different from a consensus failure, and Solscan’s authoritative on-chain data helps clarify which is occurring.
Best practices for continuous validator monitoring via Solscan
Professional operators typically integrate Solscan data into monitoring dashboards that track metrics over time. Skip rate, stake amount, and slot assignment frequency can be queried daily through Solscan’s API and stored in a time-series database. Alerts trigger when skip rate exceeds a configurable threshold or when stake drops below expected levels, signaling potential delegator exit.
Setting realistic thresholds is important. A skip rate of 1 or 2 percent is normal and does not warrant alerting; 10 percent or higher demands investigation. A sudden drop in stake warrants investigation, but small fluctuations are normal. Solscan’s historical context prevents over-alerting by distinguishing between normal variance and genuine problems.
Correlating Solscan data with local validator metrics creates a complete picture. When Solscan shows high skip rates and local hardware metrics show CPU or memory saturation, the diagnosis is clear: scale the hardware. When Solscan shows normal skip rates but the operator’s local node reports lagging consensus, the issue may be the RPC endpoint the local node is using, not the validator itself. This cross-referencing transforms Solscan from a passive monitoring tool into an active diagnostic instrument.
Operators should also regularly review the broader network health visible on Solscan. Monitoring the total number of active validators, aggregate skip rates, and the top validators’ stake distribution reveals trends in the network’s structural health. Increasing concentration or rising skip rates network-wide may signal economic pressure or technical challenges that eventually affect all operators. Early awareness through Solscan allows strategic adjustments before they become urgent.
Frequently asked questions
How often does Solscan update validator and epoch data?
Solscan updates in real time as blocks are produced on the Solana network. Validator metrics such as skip rate and slot assignments are updated continuously as blocks arrive. Epoch-level metrics are finalized at epoch boundaries but can be viewed and analyzed while an epoch is still active. The block explorer is designed for live monitoring, not batch updates.
Can I use Solscan to identify why my transaction was slow to confirm?
Yes. Search for your transaction signature on Solscan to see which block it was included in, which validator produced that block, the exact fee you paid, and the timestamp. If the block was produced normally but your transaction appeared later in subsequent blocks, the issue was likely mempool competition or the validator’s processing capacity. If the block that should have contained your transaction was skipped entirely, network consensus issues may have occurred.
How should I use Solscan data to choose a validator for staking?
Review the validator’s skip rate over the past 10 epochs, current commission rate, and total stake. Prefer validators with skip rates consistently above 95 percent and stable commissions. Check whether the validator’s name and website appear professional and established. Use Solscan’s historical epoch data to confirm the validator has maintained good performance over months, not just recent weeks.