Metric Decoder
How to read the main labels
Fleet HealthDevice operationsHeartbeat freshness, online status, benchmark drift, and whether a farm is actually running cleanly.
Commitment HealthStaking deliveryCapacity versus promised workload. A manager can have healthy devices but still poor commitment coverage.
RetainedIndexed and storedServed from the explorer database so the site stays fast and survives node pruning.
LiveFresh chain-sensitive pathUsed selectively where freshness matters enough to justify the extra cost.
Explorer Model
What is live and what is retained?
The site runs a live worker that stays near finalized tip and a separate backfill worker that replays older history from the archive node. Most pages are served from retained indexed data instead of live RPC, which keeps the site fast and resilient even when the chain node is pruned.
LiveFresh finalized chain tracking, near-tip ingestion, watched-farm device status, and high-priority operational signals.
RetainedIndexed blocks, events, extrinsics, staking ledger history, summaries, and cached views that let the explorer stay responsive.
Operations
How fresh is farm monitoring?
Phone-farm monitoring is kept fresher than ordinary explorer pages. Heartbeat-oriented device status is prioritized for watched farm flows, and benchmark health is refreshed on a rolling queue so operators can actually use the fleet pages to manage devices.
Heartbeat statusOnline, stale, down, and unknown device state.
Benchmark healthCompute drift and hardware quality, not basic liveness.
Public pagesStill lean on retained and cached views where possible so the site stays fast.
Wallet History
Why can wallet history differ from current balances?
Current balances are kept exact for all accounts. Historical balance checkpoints are retained more selectively so the VPS can stay healthy and store deeper chain activity where it matters most.
Core farm wallets and community-watched accounts keep richer retained checkpoint history than the long tail of accounts nobody opens. That is why a current balance can be exact even when the retained history window is shorter.
Page Reading Guide
How should I read manager and fleet pages?
- Fleet Health is about devices: online, stale, down, benchmark drift, and operational quality.
- Commitment Health is about staking capacity versus promised workload.
- Staking Ledger is the retained movement history for delegation, withdrawals, redelegations, and slashes.
- Rewards and finance are wallet-facing retained flows into the manager wallet, not a live accounting ledger.
Navigation
Can I search partial addresses?
Yes. Search supports exact matches, prefixes, and longer address fragments. It can resolve managers, blocks, extrinsics, wallets, and processors without requiring the full identity every time.
Use the header search for quick jumps. Use Search when you want the broader result page.
Design Goal
What is the site optimized for?
Acurast Pulse is optimized for the community reality of Acurast: phone farms, managers, processors, staking, slashes, deployments, payouts, and chain activity that operators and delegators actually inspect. It is not trying to behave like a generic full-chain warehouse on the VPS.
The explorer favors speed, operational usefulness, and retained signal quality on the VPS, while deeper history can be expanded over time through archive-assisted backfill and archive-side infrastructure.
Common Misreads
Things people often confuse
“Fleet Health” and “Commitment Health” are the same thing.
No. Fleet Health is about devices. Commitment Health is about whether the manager is delivering the compute capacity it promised to delegators.
“Retained” means stale or inaccurate.
No. Retained means the data is indexed and stored locally. It is often the most efficient and reliable way to serve exact explorer history.
If balance history is selective, current balances are also selective.
No. Current balances stay exact for all accounts. What becomes selective is the depth of retained historical balance checkpoints.
Manager wallet resolution always means a single current owner wallet.
Not always. Some managers are mixed-owner groups. The explorer tries to show the primary wallet view clearly, but that does not mean the manager has only one historical owner identity.
