How to deploy Subscan Essentials on Kubernetes?

Use the official Helm Chart from the subscan-essentials-chart repository: add the repo, configure values.yaml with your database and Redis details, then install or upgrade the chart. It supports multi-network setups and custom resources.

Subscan Essentials vs Polkascan: which should I use?

Subscan Essentials is a self-hostable backend focused on extensibility and production use, powering subscan.io. Polkascan is another explorer framework; choose Subscan Essentials if you need proven Substrate integration and custom plugins, but expect more setup work.

Can I use Subscan Essentials for EVM-only chains?

No, it's specifically designed for Substrate-based blockchains, though it can index EVM data within Substrate parachains that support it, like Moonbeam. For pure EVM chains, other explorers are better suited.

How to add custom data plugins?

Utilize the plugin framework with auto-generated templates from the gen tool in the subscan-plugin repository. Follow the plugins documentation to build and integrate custom parsers for unique on-chain data.

What are the system requirements for running this?

Requires Linux/macOS, Go 1.23+, Redis 3.0.4+, and MySQL 8.0+ or PostgreSQL 16+. Adequate CPU and memory are needed for indexing large chains, as worker goroutines handle data processing.

Is there a hosted version available?

Not for the open-source project; it's designed for self-hosting. The team behind subscan.io may offer commercial services, but you must deploy and manage the infrastructure yourself using Docker or Kubernetes.

Open-Awesome

Subscan Go Utilities

GPL-3.0Gov0.1.0

A high-precision, self-hostable blockchain explorer scaffold for Substrate-based networks like Polkadot.

Visit Website GitHub

211 stars120 forks0 contributors

What is Subscan Go Utilities?

Subscan Essentials is a backend scaffold and API server for building high-precision blockchain explorers for Substrate-based networks like Polkadot and Kusama. It solves the problem of needing a reliable, extensible foundation to index, query, and serve on-chain data, eliminating the need to build an explorer from scratch.

Target Audience

Teams and developers building or operating blockchain explorers for Substrate parachains, solo chains, or testnets who need a production-proven, self-hostable backend.

Value Proposition

Developers choose Subscan Essentials because it's the open-source engine powering the widely-used Subscan explorer, offering battle-tested Substrate integration, a flexible plugin architecture, and multi-chain support out of the box.

Overview

Polkadot Substrate Explorer Subscan

Use Cases

Best For

Launching a dedicated block explorer for a new Substrate parachain
Self-hosting a blockchain explorer to maintain data sovereignty
Extending explorer functionality with custom data plugins
Building internal dashboards for Substrate chain analytics
Creating a testnet explorer during network development
Forking and customizing the Subscan backend for specific needs

Not Ideal For

Projects targeting non-Substrate blockchains like Ethereum or Solana
Teams needing a fully managed, SaaS block explorer without self-hosting complexity
Developers seeking an all-in-one solution with integrated backend and frontend
Environments with minimal infrastructure or strict resource constraints

Pros & Cons

Pros

Production-Proven Integration

Powers the widely-used subscan.io service, ensuring battle-tested reliability for indexing Substrate blockchains, including blocks, extrinsics, and EVM data.

Extensible Plugin Framework

Offers a custom plugin system with auto-generated templates via the gen tool, allowing teams to easily add unique data features and parsers.

Flexible Deployment Options

Supports Docker Compose and Helm Chart for Kubernetes, along with multiple database backends (MySQL/PostgreSQL), simplifying production scaling and management.

Comprehensive API Documentation

Includes built-in HTTP API docs for developer integration, enabling seamless connection to custom frontends or analytics dashboards.

Cons

Complex Multi-Service Setup

Requires manual configuration and running of separate processes (subscribe, worker, API server) with dependencies on Redis and a relational database, increasing initial deployment time.

Separated Frontend Dependency

The React UI is in a different repository, adding an extra layer of setup and maintenance compared to integrated explorer solutions.

Steep Learning Curve for Customization

Custom type registration and plugin development assume familiarity with Substrate's SCALE codec and Go, which can hinder rapid adjustments for less experienced teams.

Frequently Asked Questions

Related Projects

Polkadot-JS API

Promise and RxJS APIs around Polkadot and Substrate based chains via RPC calls. It is dynamically generated based on what the Substrate runtime provides in terms of metadata.

Stars1,112

Forks389

Last commit21 days ago

subxt

Interact with Substrate based nodes in Rust or WebAssembly

Stars491

Forks291

Last commit4 days ago

Rust API Client

Library for connecting to substrate API over WebSockets

Stars265

Forks123

Last commit24 days ago

Python Interface

Python Polkadot SDK

Stars257

Forks124

Last commit4 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub