Blockchain Explorer of the DIVA storage layer. See
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
node14 -> node16, docker build
3 weeks ago
bin bash fixes 3 weeks ago
build fixed: build process 1 year ago
deploy fix: git merge 3 months ago
dist node14 -> node16, config fixes 3 weeks ago
src node14 -> node16, config fixes 3 weeks ago
static node14 -> node16, config fixes 3 weeks ago
test initial project, added test boilerplate 2 years ago
view dna column width bug fix, version updated 2 months ago
.editorconfig added initial view (UI) 2 years ago
.eslintrc.json added: security linter (dev only) 11 months ago
.gitignore initial 2 years ago added: code of merit 3 months ago
Dockerfile node14 -> node16, docker build 3 weeks ago
LICENSE added: documentation, license AGPLv3 1 year ago docs updated: building/running/docker 3 weeks ago
package-lock.json node14 -> node16, config fixes 3 weeks ago
package.json node14 -> node16, config fixes 3 weeks ago
tsconfig.json node14 -> node16, docker build 3 weeks ago

DIVA Blockchain Explorer

User Interface to explore the DIVA Blockchain.

See DIVA Testnet on


The configuration can be controlled using environment variables.


Default: warn

Available levels: trace, info, warn, error, critical




Default: 3920




Default: ws://


To build a binary on Linux (amd64) within the build/ folder, use bin/


On Linux amd64: build it first, then execute bin/explorer-linux-amd64. Set the environment variables (see configuration above) like this LOG_LEVEL=trace bin/explorer-linux-amd64.

Docker (all platforms): docker run -p 3920:3920 -d --name diva-explorer divax/explorer:current. Adapt the port exposure (-p) and the name (--name) to your needs. Use --env to set the environment variables within the container. IMPORTANT: a docker network is required (see docker docs) to let the explorer communicate with the blockchain backend running in another docker container. For beginners, it might be easier to use the DIVA Dockerized project to get started.


Remark: credentials (like username and password, ssh keys or tokens) are needed to deploy packages. The helper scripts are created to support automated deployment but do not contain any credentials.

  • Docker: to create docker images, use bin/


Contributions are very welcome. This is the general workflow:

  1. Fork from
  2. Pull the forked project to your local developer environment
  3. Make your changes, test, commit and push them
  4. Create a new pull request on

It is strongly recommended to sign your commits:

If you have questions, please just contact us (see below).


Your donation goes entirely to the project. Your donation makes the development of DIVA.EXCHANGE faster. Thanks a lot.




or via




Contact the Developers

On DIVA.EXCHANGE you'll find various options to get in touch with the team.

Talk to us via Telegram (English or German).