The explorer provides a comprehensive and easy to use interface for the upcoming Ethereum beacon chain. It makes it easy to view proposed blocks, follow attestations and monitor your staking activity.
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 Ethereum chain where closed source block explorers dominate the market we decided to make our explorer open source and available for everybody.
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 Ethereum ecosystem matures we will be able to provide stronger guarantees about the updatability of the explorer.
-
General
- Open Source (GNU General Public License v3.0)
- Supports Execution Layer and Consensus Layer
- Supports multiple networks
- Written in Golang
-
Website
- Validator Dashboard with status, income, balance, attestations, proposals and charts
- Overviews about blocks, slots, epochs, transactions, validators, slashings and the mempool
- Stats and info about Rocket Pool, staking services, MEV relays and Ethereum clients
- Leaderboards about validators and deposits
- Charts about various stats
-
Monitoring
- The monitoring feature analyzes blockchain data and (optionally) data provided by a user's staking setup
- Highly configurable notifications and notification channels (mobile push, email, webhooks)
-
Tools
- APIs for Execution Layer and Consensus Layer
- Ethereum Staking Pool benchmark and overview
- Income History
- Profit Calculator
- Block Visualizer [1] [2]
- Unit Converter
- Graffiti Wall
-
- Open Source (GNU General Public License v3.0)
- Dashboard with similar info as the website
- Notifications about client updates
- Advanced Rocket Pool features
- Machine stats with charts
- Widgets
- Themes
- 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)
We currently do not provide any pre-built binaries of the explorer. Docker images are available at https://hub.docker.com/repository/docker/gobitfly/eth2-beaconchain-explorer.
- Download the latest version of the Prysm beacon chain client and start it with the
--archive
flag set - Wait till the client finishes the initial sync
- Setup a PostgreSQL DB and import the
tables.sql
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.
-
Clone the repository
-
Run
docker-compose up
to start instances of the following containerseth1
,prysm
,postgres
andgolang
. -
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 0.0.0.0 -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
prysm
instance. -
Copy the
config-example.yml
file and adapt it to your environment.
In your.yml
file specifyeth1Endpoint
as'./private/eth1_node/.ethereum/goerli/geth.ipc'
. For database information checkpostgres
section indocker-compose.yml
file. -
Connect to
golang
instance by runningdocker exec -ti golang bash
and runmake all
-
Start the explorer binary and pass the path to the config file as argument
./bin/explorer --config your_config.yml
Install golint. (see https://github.com/golang/lint)
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).