OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Explorers & Analytics

Dcrdata

Dcrdata is a Go-based Decred block explorer and data service that collects and stores blockchain data, monitors the mempool, and provides RESTful JSON APIs.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Dcrdata — OpenViST project profile in Explorers & Analytics.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Choose dcrdata when you need a self-hosted Decred explorer or data service and can operate it alongside a synchronized dcrd node and PostgreSQL.

Who it is for

  • People who need a web interface for exploring Decred blocks and transactions.
  • Operators who want to collect and index Decred data for an explorer or API service.
  • Developers building applications that consume Decred blockchain data or mempool information.

Documented uses

  • Present Decred blockchain information through a block explorer.
  • Collect, index, and store blockchain data using a PostgreSQL backend.
  • Monitor and report on mempool activity.
  • Provide Decred data through RESTful JSON APIs.
Before you choose

Requirements & limits

The project is an open-source public repository under the ISC license. Its README documents server-side prerequisites and build requirements.

  • A synchronized dcrd node with txindex enabled is required for transaction details and address searches.
  • PostgreSQL 11 or later is required; a fresh database performs a bulk import and indexing on startup.
  • The README advises not to interrupt initial synchronization or use the browser interface before it finishes.
  • Go 1.20 or 1.21 is listed for building; Node.js 16 or later is used to package web assets and is not needed at runtime.
  • The README recommends an SSD, preferably NVMe, for PostgreSQL workloads and says the supplied Dockerfiles are not supported.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build dcrdata’s static web assets

Prepare the bundled static web assets used by dcrdata.

Before you start

  • Node.js 16.x or later and npm.
  • A cloned dcrdata repository.
  • A Unix-like shell.

Steps

  1. Change to the cmd/dcrdata directory.

  2. Install the Node.js build dependencies with the command below.

    Documented command
    npm clean-install

  3. Create the production Webpack bundle with the command below.

    Documented command
    npm run build

Expected outcome

The bundled static assets are created in `cmd/dcrdata/public/dist`.

Guide limitations

  • This recipe builds the static assets only; it does not build or start the dcrdata executable.
  • Dockerfiles are provided but are not supported.
  • Node.js is a build tool and is not used at runtime.
Documentation 1 ↗
Source-based practical guide

Configure and start dcrdata for initial blockchain indexing

Set up the documented configuration and start dcrdata so it can perform its initial database import and indexing.

Before you start

  • A running, synchronized dcrd with transaction indexing enabled (txindex=1).
  • PostgreSQL 11 or later, configured for the hardware and dcrdata workload.
  • A built dcrdata executable and its sample configuration file.
  • For dcrdata and PostgreSQL on the same host, an SSD with at least 120 GB free space; the README recommends NVMe.

Steps

  1. Carefully review the repository’s PostgreSQL tuning guidance and edit the existing PostgreSQL configuration for the system; do not replace the configuration file by copying tuning settings wholesale.

  2. Copy sample-dcrdata.conf to ~/.dcrdata/dcrdata.conf on Linux using the default appdata directory, then edit it with the dcrd RPC settings.

  3. Ensure txindex=1 is set in dcrd.conf and that dcrd is running and synchronized.

  4. Launch dcrdata with ./dcrdata and allow the initial import and indexing to complete without interruption or browser use.

Expected outcome

On a fresh PostgreSQL-backed startup, dcrdata automatically imports blockchain data and generates table indexes; subsequent launches process only blocks new to dcrdata.

Guide limitations

  • The README warns that interrupting the initial sync or using the browser interface before completion can leave dcrdata and its databases in an unrecoverable or suboptimal state.
  • Initial synchronization time varies with hardware and software; the README gives a typical range of 1.5 to 8 hours.
  • Without the required dcrd indexes, transaction details and address searches are unavailable and dcrdata exits with an error.
  • The README says to use a current release or stable branch, not master in production.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for Blockchain exploration

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
DcrdataPresent Decred blockchain information through a block explorer.CLI, Linux, Self-hosted, ServerThe project is an open-source public repository under the ISC license. Its README documents server-side prerequisites and build requirements.
ChainlensExplore a supported blockchain network through a dashboard.Docker, Self-hosted, ServerThe free edition is described as free for non-commercial use and evaluation. Its deployment configuration supports Docker Compose or Kubernetes. Web3 Labs separately describes hosted plans; commercial-use inquiries are directed to the provider.
EthvmExplore Ethereum blockchain data through a client-side block explorer.Self-hosted, Server, Web
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
8 October 2026
Original website title
decred/dcrdata · Official homepage title · retained in its source language
How we review sourcesSuggest a correction