General Requirements

You have run the zcashd node with some additional additional features enabled that will allow it to support the explorer. A block-explorer-enabled zcashd can perform all the functions of a normal zcashd node but typically will not be used as a wallet (will contain no private keys).

additional flags to enable on your zcash.conf file

ztxindex=1
experimentalfeatures=1
insightexplorer=1
paymentdisclosure=1

Additionally make sure rpcuser , rpcpassword and rpcport are configured , the same should me made available in the explorer config.

rpcuser=<username>
rpcpassword=<password>
rpcport=83232

to know more about these features, please refer to https://zcash.readthedocs.io/en/latest/rtd_pages/insight_explorer.htmlarrow-up-righthttps://github.com/zcash/zcash/blob/master/doc/payment-disclosure.mdarrow-up-right

If you are running the explorer as Docker container or on a different server you may have to configure rpcallowip

Do note that using rpcallowip will have severe security implications. Please refer to https://zcash.readthedocs.io/en/latest/rtd_pages/zcash_conf_guide.htmlarrow-up-right Elixir dependencies:

mix.exs

Frontend dependencies ( managed using npm )

check assets/package.json

Additional requirement for Viewing Key Support.

Viewing Key feature is powered by adityapk00's zecwallet-light-cliarrow-up-right.

we spin up a Docker container that runs zecwallet-light-cli, pull the logs from the container and broadcast the logs and Tx info ( after some processing ) to the explorer. The container will be deleted after the transactions are sent to the explorer.

circle-info

this feature has rate limits and currently it's hardcoded to 10 Concurrent VK imports.

Last updated