Need help with eth2-beaconchain-explorer?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

282 Stars 173 Forks GNU General Public License v3.0 1.0K Commits 125 Opened issues


Open source golang based explorer for the eth2 beacon chain

Services available


Need anything else?

Contributors list

Eth2 Beacon Chain Explorer

The explorer provides a comprehensive and easy to use interface for the upcoming Eth2 beacon chain. It makes it easy to view proposed blocks, follow attestations and monitor your staking activity.

Badge Gitter Go Report Card


The explorer is built using golang and utilizes a PostgreSQL database for storing and indexing data. In order to avoid the situation we currently have with the Eth1 chain where closed source block explorers dominate the market we decided to make our explorer open source and available for everybody.

Eth 2.0 Testnet Explorers


Warning: The explorer is still under heavy active development. More or less everything might change without prior notice and we cannot guarantee any backwards compatibility for now. Once the eth2 ecosystem matures we will be able to provide stronger guarantees about the updatability of the explorer.



  • Bootstrap based and mobile first web interface
  • Fast and robust blockchain indexing engine, able to handle missed, duplicate & forked blocks
  • Index page
    • Auto refresh - Index page data is automatically updated every 15 seconds
    • Basic chain statistics (current epoch, current slot, active validators, pending validators, staked ether)
    • Information on the 20 most recent blocks (epoch, slot, time, proposer, hash, number of attestations, deposits, slahsings and voluntary exits)
  • Epochs page
    • Pageable tabular view of all epochs (epoch, time, blocks, attestations, slashings, exits, finalization status, voting statistics)
  • Blocks page
    • Pageable tabular view of all blocks (epoch, time, proposer, hash, attestations, slashings, exits)
  • Block page
    • Basic block info (epoch, slot, status, time, proposer, root hash, parent hash, state root hash, signature, randao reveal, graffiti, eth1 data)
    • List of attestations included in the block
    • List of deposits included in the block
    • List of LMD GHOST votes
  • Validators page
    • Pageable tabular view of all pending, active and ejected validators
  • Validator page
    • Basic validator info (index, current balance, current effective balance, status, slashed, active since, exited on)
    • Historic balance evolution chart
    • List of proposed and missed blocks
  • Visualizations
    • Live visualization of blocks being added to the blockchain


  • Add chain statistic charts
  • Improve design, move away from stock bootstrap 4
  • Use a proper open source charting library
  • Come up with a smarter exporter logic (the current logic is stupid as it simply dumps the contents of the RPC calls into the database without doing any pre-aggregation or cleanups)

Getting started

We currently do not provide any pre-built binaries of the explorer. Docker images are available at

  • Download the latest version of the Prysm beacon chain client and start it with the
    flag set
  • Wait till the client finishes the initial sync
  • Setup a PostgreSQL DB and import the
    file from the root of this repository
  • Install go version 1.13 or higher
  • Clone the repository and run
    make all
    to build the indexer and front-end binaries
  • Copy the config-example.yml file and adapt it to your environment
  • Start the explorer binary and pass the path to the config file as argument
  • To build bootstrap run
    npm run --prefix ./bootstrap dist-css
    in project folder.

Developing locally with docker

  • Clone the repository
  • Run
    docker-compose up
    to start instances of the following containers
  • Open a new terminal in project directory and run
    docker run -it --rm --net=host -v $(pwd):/src  postgres psql -f /src/tables.sql -d db -h -U postgres
    to create new tables in the database
  • Wait for the client to finish initial sync, you can check this by looking at logs of
  • Copy the
    file and adapt it to your environment.\ In your
    file specify
    . For database information check
    section in
  • Connect to
    instance by running
    docker exec -ti golang bash
    and run
    make all
  • Start the explorer binary and pass the path to the config file as argument

    ./bin/explorer --config your_config.yml


Install golint. (see

Commercial usage

The explorer uses Highsoft charts which are not free for commercial and governmental use. If you plan to use the explorer for commercial purposes you currently need to purchase an appropriate HighSoft license. We are planning to switch out the Highsoft chart library with a less restrictive charting library (suggestions are welcome).

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.