proxmox/docs/03-deployment/EXPLORER_COMPETITIVE_AUDIT_2026-04-09.md

Explorer Competitive Audit

Date: 2026-04-09

Scope:

• Product under review: SolaceScanScout / Chain 138 explorer in explorer-monorepo/
• Comparison set: Etherscan, Blockscout, Blockchain.com Explorer, Solscan, and the general top-explorer market
• Goal: translate the prior qualitative review into a decision-grade audit with a weighted rubric, a feature matrix, and a roadmap from the current 5.8/10 state to category-leading quality

Executive Summary

The current explorer is not weak, but it is mispositioned if judged as a direct Etherscan replacement.

Today it scores:

• 5.8/10 as a public blockchain explorer product
• 7.1/10 as a Chain 138-specific explorer plus operator cockpit

The product is strongest where general explorers are weakest:

• Chain 138-specific workflows
• mission-control and operator-adjacent monitoring
• bridge, liquidity, routing, wallet, and command-center tie-ins

The product is weakest where users expect top explorers to be strongest:

• transaction depth
• address depth
• token intelligence
• contract tooling
• analytics richness
• trust, polish, and “power-user completeness”

Important interpretation:

• 10/10 means category-leading explorer quality on a normal scale
• 14/10 is not a literal score; it is a shorthand for “best-in-class explorer plus differentiated platform moat”
• The realistic path is:
  1. move from 5.8/10 to 8/10 by closing obvious explorer gaps
  2. move from 8/10 to 10/10 by reaching explorer-category parity
  3. move from 10/10 to the “14/10” vision by adding unique Chain 138 and operator-native capabilities no major explorer currently combines

Evidence Base

This audit is based on:

• Local product surface in:
  • explorer-monorepo/frontend/src/pages/
  • explorer-monorepo/frontend/src/components/
  • explorer-monorepo/frontend/src/services/api/
  • explorer-monorepo/backend/api/rest/swagger.yaml
• Recent public benchmark sources:
  • Etherscan feature index: https://info.etherscan.com/25-etherscan-features-in-2025
  • Etherscan watch list: https://info.etherscan.com/watch-list/
  • Etherscan private tags: https://info.etherscan.com/private-address-name-tags/
  • Blockscout verification docs: https://docs.blockscout.com/devs/verification
  • Blockscout verification API: https://docs.blockscout.com/devs/verification/blockscout-smart-contract-verification-api
  • Blockscout contract interaction docs: https://docs.blockscout.com/devs/verification/interacting-with-smart-contracts
  • Blockscout watch list docs: https://docs.blockscout.com/using-blockscout/my-account/watchlist
  • Blockchain.com Explorer: https://www.blockchain.com/explorer
  • Blockchain.com charts: https://www.blockchain.com/explorer/charts/n-transactions
  • Blockchain.com mempool charts: https://www.blockchain.com/explorer/charts/mempool-size
  • Solscan analytics dashboard docs: https://docs.solscan.io/browsing-the-site/solscan-knowledge-base/general/analytic-dashboard

Current Product Snapshot

The explorer already provides a real product skeleton, not just a demo:

• core navigation and route coverage
• blocks, transactions, addresses, search, tokens, and watchlist pages
• mission-control, routes, bridge, liquidity, pools, analytics, operator, and wallet surfaces
• Blockscout-backed explorer data with a Chain 138 RPC-aware fallback for missing transactions
• stronger dead-end handling than before the recent fixes

Representative local implementation points:

• navigation: explorer-monorepo/frontend/src/components/common/Navbar.tsx
• tx detail: explorer-monorepo/frontend/src/pages/transactions/[hash].tsx
• address detail: explorer-monorepo/frontend/src/pages/addresses/[address].tsx
• search: explorer-monorepo/frontend/src/pages/search/index.tsx
• tokens: explorer-monorepo/frontend/src/pages/tokens/index.tsx
• watchlist: explorer-monorepo/frontend/src/pages/watchlist/index.tsx
• analytics shell: explorer-monorepo/frontend/src/components/explorer/AnalyticsOperationsPage.tsx
• API contract: explorer-monorepo/backend/api/rest/swagger.yaml

Weighted Score Rubric

Scoring model:

• Each category is scored from 0 to 10
• Weighted total is the sum of score/10 * weight
• Maximum weighted total = 100
• Final product score = weighted total divided by 10

Category Weights

Category	Weight	What “10/10” Means
Core navigation and discoverability	10	Users can move anywhere important with near-zero dead ends or ambiguity
Search and entity resolution	10	Fast, accurate, direct, and forgiving lookup across addresses, txs, blocks, tokens, contracts, labels
Transaction detail depth	15	Rich tx page with internal txs, logs, decoded methods/events, token transfers, traces, failure diagnostics
Address and account intelligence	15	Portfolio, holdings, activity segmentation, labels, approvals, analytics, exports, and useful pivots
Token and asset explorer quality	10	Holders, transfers, metadata, market context, trust signals, supply, and route/liquidity context
Contract and developer tooling	10	Verification, source browsing, ABI UX, read/write contract, API confidence, docs, and developer trust
Analytics and data storytelling	10	Charts, dashboards, trends, protocol/network insights, and explainable metrics
Performance, reliability, and dead-end handling	10	Pages load consistently, degraded states are explicit, broken routes are rare, and fallbacks are credible
UX polish and trustworthiness	10	Feels premium, coherent, legible, and “safe to rely on” for serious work

Current Weighted Scores

Category	Weight	Current Score	Weighted Result	Notes
Core navigation and discoverability	10	7.5	7.5	Good routing coverage and better onward navigation than before
Search and entity resolution	10	7.0	7.0	Strong direct matching, but broad search depth is still limited
Transaction detail depth	15	4.5	6.75	Lacks traces, decoded logs, token transfer tabs, and contract interaction context
Address and account intelligence	15	5.0	7.5	Useful basics, but not a power-user account page
Token and asset explorer quality	10	3.5	3.5	Mostly shortcut/search behavior, not a mature token explorer
Contract and developer tooling	10	3.5	3.5	Some backend signals exist, but not exposed as top-tier user tooling
Analytics and data storytelling	10	4.5	4.5	Thin dashboard, limited explanatory analytics
Performance, reliability, and dead-end handling	10	6.5	6.5	Improved meaningfully, but still not elite
UX polish and trustworthiness	10	5.3	5.3	Coherent enough, but still feels niche and partially assembled
Total	100		58.05	5.8/10 overall

Competitive Positioning

Score Summary

Product	Score	Position
Etherscan	9.4	Category leader for general EVM explorer utility
Strong Blockscout deployment	8.2	Best open-source explorer baseline, especially for teams that expose full contract tooling well
Solscan	8.0	Strong ecosystem-native explorer with better analytics and account views
Blockchain.com Explorer	7.0	Strong macro-market and network-stat presentation, weaker as an EVM contract explorer benchmark
SolaceScanScout current	5.8	Good niche product, not yet a category-leading explorer

Feature-By-Feature Competitor Matrix

Legend:

• Strong = mature, expected, competitive
• Partial = present but thin, inconsistent, or not power-user grade
• Weak = noticeable gap
• Unique = differentiator not commonly found in the comparison set

Capability	SolaceScanScout	Etherscan	Strong Blockscout	Blockchain.com	Solscan	Notes
Global nav clarity	Partial	Strong	Strong	Strong	Strong	Current nav is good, but product identity is split between explorer and ops console
Direct address / tx / block search	Strong	Strong	Strong	Strong	Strong	Current direct-match behavior is solid
Fuzzy / broad search depth	Partial	Strong	Strong	Partial	Strong	Needs better entity breadth and ranking
Block list and block detail	Partial	Strong	Strong	Strong	Strong	Adequate, but not insight-rich
Transaction detail basics	Partial	Strong	Strong	Partial	Strong	Hash, from/to, status, gas are present
Internal transactions / traces	Weak	Strong	Strong	Weak	Partial	Major gap
Decoded method and event logs	Weak	Strong	Strong	Weak	Strong	Major gap
Token transfer tabs in tx view	Weak	Strong	Strong	Weak	Strong	Major gap
Tx failure diagnostics	Partial	Strong	Partial	Weak	Partial	Current missing-tx diagnosis is a good start, but not full execution diagnostics
Address overview basics	Partial	Strong	Strong	Partial	Strong	Present but shallow
Address holdings / balances view	Weak	Strong	Strong	Partial	Strong	Major gap
Address analytics tab	Weak	Strong	Partial	Weak	Strong	Major gap
Labels / tags / private notes	Partial	Strong	Strong	Weak	Partial	Watchlist exists, but labeling workflow is light
Watchlist	Strong	Strong	Strong	Weak	Strong	Local watchlist is a meaningful strength
Token pages	Weak	Strong	Strong	Partial	Strong	Current token page is mostly search scaffolding
Token holders / transfers	Weak	Strong	Strong	Weak	Strong	Major gap
Contract verification UX	Weak	Strong	Strong	Weak	Partial	Backend hints exist, but user-facing flow is not there
Read / write contract	Weak	Strong	Strong	Weak	Partial	Major gap
API and docs trust	Partial	Strong	Strong	Partial	Strong	Swagger exists, but developer experience is not yet elite
Network / macro analytics	Partial	Strong	Partial	Strong	Strong	Current analytics are useful but thin
Chain-specific operational tooling	Unique	Weak	Partial	Weak	Partial	This is where the product can win
Bridge / liquidity / route intelligence	Unique	Weak	Weak	Weak	Partial	Real differentiation opportunity
Graceful degraded states	Partial	Strong	Partial	Strong	Strong	Improved recently, still not best-in-class
Overall trust and polish	Partial	Strong	Strong	Strong	Strong	The product still feels niche instead of inevitable

Strengths To Preserve

These are not just “nice extras”; they are the seeds of the product moat:

• Chain 138-aware transaction diagnostics
• explorer plus bridge plus liquidity plus routes plus mission-control in one place
• operator-adjacent functionality that can grow into a real command surface
• watchlist and navigation improvements that reduce dead ends
• practical bridge and route orientation for actual chain usage, not just passive observation

Biggest Gaps

These are the highest-impact reasons the product trails top explorers:

1. Transaction pages are not yet “investigation pages.” They show basics, but not the execution narrative users expect.

2. Address pages are not yet “entity pages.” They do not explain what an address holds, does, approves, or influences.

3. Token pages are not yet real token explorer pages. They are mostly routing/search entry points.

4. Contract and developer tooling are too hidden or too thin. The product does not yet feel developer-serious in the way Etherscan and top Blockscout deployments do.

5. Analytics are present as tiles, not as a real data product. They inform, but they do not yet reveal.

Exact Roadmap

This roadmap is ordered by score impact, user value, and implementation leverage.

Phase 1: Move From 5.8/10 To 8/10

Target outcome:

• eliminate the most obvious reasons a serious user bounces back to Etherscan or a raw Blockscout page

1. Make transaction pages investigation-grade

Add to transactions/[hash].tsx and supporting APIs:

• token transfer section
• internal transactions / trace section
• decoded method name and arguments
• decoded event logs
• revert reason or failure summary when available
• expandable raw input and receipt JSON
• next/previous pivots:
  • block
  • from address
  • to address
  • created contract

Expected score lift:

• transaction detail from 4.5 to 7.5

2. Make address pages entity-grade

Add to addresses/[address].tsx and supporting APIs:

• token balances section
• contract vs EOA behavior summary
• incoming vs outgoing activity summary
• latest token transfers
• internal tx tab
• approvals / allowances tab if data is available
• labels / notes / watchlist metadata layer
• export CSV / JSON for recent activity

Expected score lift:

• address intelligence from 5.0 to 7.0

3. Replace the token shortcut page with real token explorer pages

Implement:

• token detail route by address
• token overview with symbol, supply, holders count, transfers count
• holders table
• recent transfers
• related pools / routes / liquidity context
• trust and provenance badges for Chain 138-curated assets

Expected score lift:

• token quality from 3.5 to 7.0

4. Tighten search into an explorer-grade finder

Add:

• entity grouping in results
• better ranking for exact match vs partial match
• support for token symbols, labels, and curated contract aliases
• “did you mean” behavior for malformed inputs
• explicit no-result fallback actions per entity type

Expected score lift:

• search from 7.0 to 8.0

5. Remove remaining trust dents

Finish:

• full dead-link audit
• all public links verified
• uniform loading / empty / error states
• ensure every page has onward navigation
• no route that returns a vague failure without recommended next action

Expected score lift:

• reliability/dead-end handling from 6.5 to 8.0
• UX trust from 5.3 to 6.5

Phase 2: Move From 8/10 To 10/10

Target outcome:

• the product feels credible beside a strong Blockscout deployment and respectable beside Etherscan for daily use

6. Ship contract and developer power tools

Add:

• verified contract page enhancements
• source code browser
• ABI tab
• read contract
• write contract
• verification submission UX
• contract diff / similar-match support where possible
• first-class API docs and working examples

Expected score lift:

• contract/developer tooling from 3.5 to 8.0

7. Make analytics a real product surface

Add:

• chain activity charts
• transaction throughput and gas trends
• token and bridge flows
• top contracts / top tokens / top counterparties
• route and liquidity health trends
• anomaly callouts
• downloadable snapshots for operators and analysts

Expected score lift:

• analytics from 4.5 to 8.0

8. Add account intelligence features users expect from leaders

Add:

• saved labels and notes
• notification hooks or webhook/email alerts
• approval risk surfaces
• address clustering or relationship hints
• better wallet-oriented views

Expected score lift:

• address intelligence from 7.0 to 8.5
• UX trust from 6.5 to 8.0

Phase 3: Move Beyond 10/10 Into The “14/10” Vision

Target outcome:

• the explorer is no longer trying to be a smaller Etherscan
• it becomes the canonical Chain 138 intelligence and action layer

This phase should not be interpreted as “add more random features.” It means creating a product class that top explorers do not currently own.

9. Fuse explorer data with actionability

Turn pages into decision surfaces:

• from a token page:
  • inspect
  • route
  • add to wallet
  • view liquidity
  • simulate swap
• from an address page:
  • inspect
  • label
  • alert
  • export
  • route to related pools and contracts
• from a failed tx page:
  • diagnose
  • compare RPC views
  • suggest likely cause
  • point to next operator action

This is the product bridge between explorer and command center.

10. Make Chain 138 provenance and trust visible everywhere

Add first-class trust surfaces:

• canonical asset registry badges
• official / partner / community provenance states
• deployment source and verification lineage
• bridge origin and wrapped-asset lineage
• liquidity health and route confidence
• chain-specific token warnings that are not generic scam heuristics

This is a major opportunity because generic explorers are chain-agnostic and usually weaker here.

11. Build mission-control-quality chain intelligence into normal explorer pages

Expose:

• bridge health inline on affected asset pages
• route quality inline on token and pool pages
• chain head / indexing lag confidence on tx and block pages
• mempool, nonce, and propagation diagnostics for operators and power users
• public and operator views with progressive disclosure instead of separate product worlds

12. Create a best-in-class Chain 138 analytics graph

Add differentiated analytics no mainstream explorer fully combines:

• token flow graph for canonical assets
• bridge flow graph
• liquidity topology graph
• route availability and degradation history
• deployment and contract registry coverage maps
• “what changed today” chain summary for operators and analysts

13. Become the Chain 138 developer home, not just the public explorer

Add:

• SDK snippets from every relevant page
• verified ABI download and copy surfaces
• per-page API examples
• explorer-linked runbooks for operator-grade diagnostics
• issue reporting and metadata correction workflow

Recommended Score Targets By Phase

Phase	Target Score	Meaning
Current	5.8	Useful niche explorer, clearly below top-tier leaders
Phase 1 complete	8.0	Strong public explorer for daily Chain 138 use
Phase 2 complete	9.5 to 10.0	Category-leading explorer for its ecosystem
Phase 3 complete	“14/10” vision	Explorer plus command center plus asset-intelligence moat

What To Build First

If only a few streams can run immediately, the highest-yield order is:

1. transaction detail depth
2. address intelligence
3. real token pages
4. contract tooling
5. analytics overhaul
6. provenance / trust layer
7. explorer-to-action workflows

Product Recommendation

Do not market this as “another Etherscan.”

The stronger positioning is:

• the canonical Chain 138 explorer
• the intelligence layer for Chain 138 assets, routes, and bridge state
• the command surface for both public users and serious operators

That positioning supports the “14/10” roadmap because it aims at a broader and more defensible product than a generic explorer clone.

Short Conclusion

The explorer is already good enough to be useful. It is not yet good enough to feel inevitable.

The shortest path to a much stronger product is not visual redesign alone. It is deeper transaction pages, deeper address pages, real token intelligence, and contract/developer tooling.

The path to “14/10” is then to stop competing on generic parity alone and win on Chain 138-native intelligence, trust, and actionability.