janoside / btc-rpc-explorer

Database-free, self-hosted Bitcoin explorer, via RPC to Bitcoin Core.

BTC RPC Explorer

Self-Hosted Bitcoin explorer for everyone running Bitcoin Core.

---

This is a self-hosted explorer for the Bitcoin blockchain, driven by RPC calls to your own Bitcoin node. It is easy to run and can be connected to other tools (like Electrum servers) to achieve a full-featured explorer.

Whatever reasons you may have for running a full node (trustlessness, technical curiosity, supporting the network, etc) it's valuable to appreciate the fullness of your node. With this explorer, you can explore not just the blockchain database, but also explore all of the functional capabilities of your own node.

Live demos:

• BitcoinExplorer.org / testnet / signet

Features

• Network Summary dashboard
• View details of blocks, transactions, and addresses
• Analysis tools for viewing stats on blocks, transactions, and miner activity
• JSON REST API
• See raw JSON content from bitcoind used to generate most pages
• Search by transaction ID, block hash/height, and address
• Optional transaction history for addresses by querying from Electrum-protocol servers (e.g. Electrs, ElectrumX), blockchain.com, blockchair.com, or blockcypher.com
• Mempool summary, with fee, size, and age breakdowns
• RPC command browser and terminal

Changelog / Release notes

See CHANGELOG.md.

Getting started

Prerequisites

1. Install Bitcoin Core - instructions. Ensure that Bitcoin Core's' RPC server is enabled (server=1).
2. Allow Bitcoin Core to synchronize with the Bitcoin network (you can use this tool while sychronizing, but some pages may fail).
3. Install Node.js (16+ required, 18+ recommended).

Note about pruning and indexing configurations

This tool is designed to work best with full transaction indexing enabled (txindex=1) and pruning disabled. However, if you're running Bitcoin Core v0.21+ you can run without txindex enabled and/or with pruning enabled and this tool will continue to function, but some data will be incomplete or missing. Also note that such Bitcoin Core configurations receive less thorough testing.

In particular, with pruning enabled and/or txindex disabled, the following functionality is altered:

• You will only be able to search for mempool, recently confirmed, and wallet transactions by their txid. Searching for non-wallet transactions that were confirmed over 3 blocks ago is only possible if you provide the confirmed block height in addition to the txid.
• Pruned blocks will display basic header information, without the list of transactions. Transactions in pruned blocks will not be available, unless they're wallet-related. Block stats will only work for unpruned blocks.
• The address and amount of previous transaction outputs will not be shown, only the txid:vout.
• The mining fee will only be available for unconfirmed transactions.

Install / Run

If you're running on mainnet with the default datadir and port, the default configuration should Just Work. Otherwise, see the Configuration section below.

Install via npm:

Note: npm v7+ is required

npm install -g btc-rpc-explorer
btc-rpc-explorer

Run from source:

1. git clone https://github.com/janoside/btc-rpc-explorer
2. cd btc-rpc-explorer
3. npm install
4. npm start

Install via AUR Arch Linux:

Note: The below AUR package was created and is maintained by @dougEfresh. The details and history of the package can be seen here.

1. git clone https://aur.archlinux.org/btc-rpc-explorer.git
2. cd btc-rpc-explorer
3. makepkg -csi
4. systemctl enable --now btc-rpc-explorer

After a default installation+startup using any of the above methods, the app can be viewed at http://127.0.0.1:3002/

Configuration

Configuration options may be set via environment variables or CLI arguments.

Configuration with environment variables

To configure with environment variables, you need to create one of the 2 following files and enter values in it:

1. ~/.config/btc-rpc-explorer.env
2. .env in the working directory for btc-rpc-explorer

In either case, refer to .env-sample for a list of the options and formatting details.

Configuration with CLI args

For configuring with CLI arguments, run btc-rpc-explorer --help for the full list of options. An example execution is:

btc-rpc-explorer --port 8080 --bitcoind-port 18443 --bitcoind-cookie ~/.bitcoin/regtest/.cookie

Demo site settings

To match the features visible on the demo site at BitcoinExplorer.org you'll need to set the following non-default configuration values:

BTCEXP_DEMO=true 		# enables some demo/informational aspects of the site
BTCEXP_NO_RATES=false		# enables querying of exchange rate data
BTCEXP_SLOW_DEVICE_MODE=false	# enables resource-intensive tasks (UTXO set query, 24hr volume querying) that are inappropriate for "slow" devices
BTCEXP_ADDRESS_API=electrum 	# use electrum-protocol servers for address lookups
BTCEXP_ELECTRUM_SERVERS=tcp://your-electrum-protocol-server-host:50001		# address(es) for my electrum-protocol server(s)
BTCEXP_IPSTACK_APIKEY=your-api-key		# enable peer ip geo-location
BTCEXP_MAPBOX_APIKEY=your-api-key		# enable map of peer locations

SSO authentication

You can configure SSO authentication similar to what ThunderHub and RTL provide. To enable it, make sure BTCEXP_BASIC_AUTH_PASSWORD is not set and set BTCEXP_SSO_TOKEN_FILE to point to a file write-accessible by btc-rpc-explorer. Then to access btc-rpc-explorer, your SSO provider needs to read the token from this file and set it in URL parameter token. For security reasons the token changes with each login, so the SSO provider needs to read it each time!

After successful access with the token, a cookie is set for authentication, so you don't need to worry about it anymore. To improve user experience you can set BTCEXP_SSO_LOGIN_REDIRECT_URL to the URL of your SSO provider. This will cause users to be redirected to your login page if needed.

Run via Docker

1. docker build -t btc-rpc-explorer .
2. docker run -it -p 3002:3002 -e BTCEXP_HOST=0.0.0.0 btc-rpc-explorer

Reverse proxy with HTTPS

See instructions here for using nginx+certbot (letsencrypt) for an HTTPS-accessible, reverse-proxied site.

Support

If you get value from this project, please consider supporting my work with a donation. All donations are truly appreciated.

Donate via BTC Pay Server:

• https://donate.bitcoinexplorer.org

Or, via a lightning address:

[email protected]

btc-rpc-explorer's Issues

Getting Error When Trying To View Individual Blocks

visiting an individual block url, such as http://127.0.0.1:3002/block-height/535967, results in the following error:

/Users/redacted/Development/btc-rpc-explorer/views/includes/transaction-io-details.pug:10 8| each txInput, txInputIndex in txInputs 9| if (txInput) > 10| - var vout = txInput.vout[tx.vin[txInputIndex].vout]; 11| if (vout.value) 12| - totalInputValue = totalInputValue.plus(new Decimal(vout.value)); 13| Cannot read property 'undefined' of undefined

TypeError: /Users/redacted/Development/btc-rpc-explorer/views/includes/transaction-io-details.pug:10
    8| each txInput, txInputIndex in txInputs
    9| 	if (txInput)
  > 10| 		- var vout = txInput.vout[tx.vin[txInputIndex].vout];
    11| 		if (vout.value)
    12| 			- totalInputValue = totalInputValue.plus(new Decimal(vout.value));
    13| 

Cannot read property 'undefined' of undefined
    at eval (eval at wrap (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:1145:24)
    at eval (eval at wrap (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:1170:4)
    at eval (eval at wrap (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:2483:4)
    at template (eval at wrap (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:2900:72)
    at Object.exports.renderFile (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug/lib/index.js:427:38)
    at Object.exports.renderFile (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug/lib/index.js:417:21)
    at exports.__express (/Users/redacted/Development/btc-rpc-explorer/node_modules/pug/lib/index.js:464:11)
    at View.app.engine (/Users/redacted/Development/btc-rpc-explorer/app.js:39:23)
    at View.render (/Users/redacted/Development/btc-rpc-explorer/node_modules/express/lib/view.js:135:8)
    at tryRender (/Users/redacted/Development/btc-rpc-explorer/node_modules/express/lib/application.js:640:10)
    at Function.render (/Users/redacted/Development/btc-rpc-explorer/node_modules/express/lib/application.js:592:3)
    at ServerResponse.render (/Users/redacted/Development/btc-rpc-explorer/node_modules/express/lib/response.js:1008:7)
    at /Users/redacted/Development/btc-rpc-explorer/routes/baseActionsRouter.js:405:8
    at process._tickCallback (internal/process/next_tick.js:109:7)

As a sanity check, the RPC calls to my node for getblockhash and getblock work fine via curl. Running macOS Sierra. Any thoughts?

Thanks for a great tool!

Node status is throwing an error

The node-status page is throwing an error

Cross-link "Fun" items and "Special" blocks/txs

"historicalData" and "specialBlocks/specialTransactions" should pull from a single data source and cross-link.

Whitelist RPC calls on the RPC terminal

I accidentally killed it by sending the stop RPC command (sorry for that).

You should build a whitelist of authorized RPC calls, excluding stop, wallet calls and such.

package-lock.json should be committed

The package-lock.json file is supposed to be commited so the modules/libs versions are defined.

Improve formatting on small screens for Block and Tx pages

Add peer details page

Add support for viewing the mempool

Add detailed address info

Since bitcoind cant provide info on arbitrary address, you can rely on electrumx indexes (also works off bitcoind).
Here's an example: https://github.com/Overtorment/nodejs-electrum-http

Cannot read property 'vin' of undefined

I can not write pug code, but I encounter this problem. The problem is viewing some blocks is working well but others not.

/Users/scrapup/cpp/bti/btc-rpc-explorer/views/includes/block-content.pug:126 124| div(class="row") 125| div(class="col-md-6") > 126| h6 Input (#{tx.vin.length.toLocaleString()}) 127| if (result.txInputsByTransaction[tx.txid]) 128| - var totalInputValue = new Decimal(0); 129| table(class="table mb-0") Cannot read property 'vin' of undefined

TypeError: /Users/scrapup/cpp/bti/btc-rpc-explorer/views/includes/block-content.pug:126
    124| 						div(class="row")
    125| 							div(class="col-md-6")
  > 126| 								h6 Input (#{tx.vin.length.toLocaleString()})
    127| 								if (result.txInputsByTransaction[tx.txid])
    128| 									- var totalInputValue = new Decimal(0);
    129| 									table(class="table mb-0")

Cannot read property 'vin' of undefined

Socket Hangups for RPC calls

While trying to access http://localhost:8332
I get the following error and unable to access the website through browser.

Error for RPC command 'getchaintxstats': Error: socket hang up
Error for RPC command 'getchaintxstats': Error: socket hang up
Error for RPC command 'getblockchaininfo': Error: socket hang up
Unhandled Rejection at: Promise Promise {
{ Error: socket hang up
at createHangUpError (_http_client.js:322:15)
at Socket.socketOnEnd (_http_client.js:425:23)
at Socket.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1085:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
cause:
{ Error: socket hang up

Timeout Error with Raspberry Pi

Setup

Raspberry Pi 3 B+ with external HDD (1TB)
Linux raspberrypi 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 armv7l GNU/Linux
Nodejs: v8.11.1
Npm: 6.4.1
Bitcoin Core Daemon version v0.17.99.0-bb0277819

When trying to connect to the Website with my Browser, I get this error. My suspicion is that my Raspberry Pi ist just very slow since the SD card and HDD are not the fastest. I have it running with Litecoin on my other Raspberry Pi without problems.

Error Message

Unhandled Rejection at: Promise Promise {
_bitField: 154402816,
_fulfillmentHandler0:
{ Error: ESOCKETTIMEDOUT
at ClientRequest. (/home/pi/btc-rpc-explorer/node_modules/request/request.js:813:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at Socket.emitTimeout (_http_client.js:711:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Socket.emit (events.js:208:7)
at Socket._onTimeout (net.js:420:8)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5)
cause: { Error: ESOCKETTIMEDOUT
at ClientRequest. (/home/pi/btc-rpc-explorer/node_modules/request/request.js:813:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at Socket.emitTimeout (_http_client.js:711:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Socket.emit (events.js:208:7)
at Socket._onTimeout (net.js:420:8)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5) code: 'ESOCKETTIMEDOUT', connect: false },
isOperational: true,
code: 'ESOCKETTIMEDOUT',
connect: false },
_rejectionHandler0: undefined,
_promise0: undefined,
_receiver0: undefined,
_boundTo:
Client {
agentOptions: undefined,
auth:
{ pass: 'xxx=',
user: 'xxx' },
hasNamedParametersSupport: false,
headers: false,
host: '127.0.0.1',
password: 'xxx=',
port: 8332,
timeout: 5000,
ssl: { enabled: false, strict: false },
request:
{ [Function]
get: [Function],
head: [Function],
post: [Function],
put: [Function],
patch: [Function],
del: [Function],
delete: [Function],
cookie: [Function],
jar: [Function],
defaults: [Function],
getAsync: [Function: ret],
headAsync: [Function: ret],
postAsync: [Function: ret],
putAsync: [Function: ret],
patchAsync: [Function: ret],
delAsync: [Function: ret],
deleteAsync: [Function: ret],
cookieAsync: [Function: ret],
jarAsync: [Function: ret],
defaultsAsync: [Function: ret] },
requester: Requester { unsupported: [], version: undefined },
parser: Parser { headers: false } } } reason: { Error: ESOCKETTIMEDOUT
at ClientRequest. (/home/pi/btc-rpc-explorer/node_modules/request/request.js:813:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at Socket.emitTimeout (_http_client.js:711:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Socket.emit (events.js:208:7)
at Socket._onTimeout (net.js:420:8)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5)
cause: { Error: ESOCKETTIMEDOUT
at ClientRequest. (/home/pi/btc-rpc-explorer/node_modules/request/request.js:813:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at Socket.emitTimeout (_http_client.js:711:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Socket.emit (events.js:208:7)
at Socket._onTimeout (net.js:420:8)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5) code: 'ESOCKETTIMEDOUT', connect: false },
isOperational: true,
code: 'ESOCKETTIMEDOUT',
connect: false } stack: Error: ESOCKETTIMEDOUT
at ClientRequest. (/home/pi/btc-rpc-explorer/node_modules/request/request.js:813:19)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at ClientRequest.emit (events.js:208:7)
at Socket.emitTimeout (_http_client.js:711:34)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:106:13)
at Socket.emit (events.js:208:7)
at Socket._onTimeout (net.js:420:8)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5)

Add more detail to mempool summary

• Finer-grained details about fees
• Transaction ages
• Transaction amounts
• Technical details?

Display static/status page when btc node is starting up / verifying blocks

See error "3207fh0f".

Add live, incoming transaction view

Search fails for input with leading whitespace

Input should be trimmed for good UX.

Better handling of many-input transactions

Transactions with high numbers of inputs can cause issues when viewing block-details or transaction-details pages.

Example block:
Height 478453
Hash 000000000000000000f2f2b3f56c37ceb7566a3512d3732b1e2528a07586f9fa

Example tx:
1f7ef5e54138b77a8b7210b05e30dfde7fa03d5238e15a2b335f0926e75e0c9d

Add http rest API

So this explorer can turn into pluggable backend for light wallet clients (once additional indexing by address is added)

Optional dark theme

SyntaxError: Unexpected token [

I see the following error:

---

blk@e8020:~/Elements/work/btc-rpc-explorer$ npm start

[email protected] start /media/blk/Elements/work/btc-rpc-explorer
node ./bin/www

/media/blk/Elements/work/btc-rpc-explorer/app/utils.js:360
var [lead,decimal,pow] = val.toString().split(/e|./);
^

SyntaxError: Unexpected token [
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object. (/media/blk/Elements/work/btc-rpc-explorer/app.js:14:13)
at Module._compile (module.js:410:26)
at Object.Module._extensions..js (module.js:417:10)

npm ERR! Linux 4.10.0-32-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: node ./bin/www
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'node ./bin/www'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the btc-rpc-explorer package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./bin/www
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs btc-rpc-explorer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls btc-rpc-explorer
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /media/blk/Elements/work/btc-rpc-explorer/npm-debug.log

Graphs for detailed tx stats

Generalize RPC API to support other coins

In doing so, try to isolate BTC-specific code to more easily support other currencies in the future.

Handle uppercase TXIDs in search.

Add debug/local flag for enabling RPC console

New "block summary" and "block comparison" page

Block Summary

• Fee details
• Transaction amounts
• Technical details (segwit, address types, etc)

Block Comparison

Support for specifying several blocks and comparing their summary values.

Display list of transactions for a given address

Transaction stats: Error 500: Work queue depth exceeded

Running your fantastic block explorer on an Odroid HC2 with Debian, everything working very nicely.

Only when clicking on "Transaction stats" I can see on the console that the following error is generated, and the page is loading indefinitely.

  message: 'Internal Server Error',
  body: 'Work queue depth exceeded',
  code: 500,
  name: 'RpcError' } stack: RpcError: Internal Server Error
    at Client.rpc (/home/web/btc-rpc-explorer/node_modules/bitcoin-core/dist/src/parser.js:73:13)
    at Client.tryCatcher (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/promise.js:694:18)
    at Promise._fulfill (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/promise.js:638:18)
    at Request._callback (/home/web/btc-rpc-explorer/node_modules/bluebird/js/release/nodeback.js:45:21)
    at Request.self.callback (/home/web/btc-rpc-explorer/node_modules/request/request.js:186:22)
    at emitTwo (events.js:131:20)
    at Request.emit (events.js:214:7)
    at Request.<anonymous> (/home/web/btc-rpc-explorer/node_modules/request/request.js:1163:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage.<anonymous> (/home/web/btc-rpc-explorer/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:313:30)

No big deal, but maybe it helps to point out possible improvements.

On the third click it went through and the graphs were shown.

query changed datadir

Hi, is there a way to change the datadir, if it's not ~/.bitcoin/ ?

Add RPC API version management

App currently does not identify what version of node software it's connected to and therefore doesn't tailor itself to different versions of the RPC API. This should be changed or at least noted somehow.

Load cookie auth from daemon data dir

Allow us to specify the data dir of the coin so that you can retrieve the cookie auth. This complements docker support through a simple volume share. :)

FYI, trying to integrate this as an optional service in btcpayserver. :)

Tool for verifying signed messages

Broken regex splitting for some RPC command args lists

See https://btc-explorer.com/rpc-browser?method=getmempoolancestors

No auth mechanism defined

I am using below credentials for connecting with my btc node.

const client = new Client({
host: 'localhost',
port: 18332,
timeout: 30000,
user: 'admin',
pass: 'admin'
});

And after using this i'm getting the below error -

Unhandled rejection Error: no auth mechanism defined
at Auth.onRequest (/home/ireslab11/Desktop/node/node/node_modules/request/lib/auth.js:132:32)
at Request.auth (/home/ireslab11/Desktop/node/node/node_modules/request/request.js:1347:14)
at Request.init (/home/ireslab11/Desktop/node/node/node_modules/request/request.js:378:10)
at new Request (/home/ireslab11/Desktop/node/node/node_modules/request/request.js:127:8)
at request (/home/ireslab11/Desktop/node/node/node_modules/request/index.js:53:10)
at /home/ireslab11/Desktop/node/node/node_modules/request/index.js:61:12
at Object.apply (/home/ireslab11/Desktop/node/node/node_modules/@uphold/request-logger/src/index.js:27:19)
at Function.post (/home/ireslab11/Desktop/node/node/node_modules/request/index.js:100:12)
at Function.tryCatcher (/home/ireslab11/Desktop/node/node/node_modules/bluebird/js/release/util.js:16:23)
at Function.ret [as postAsync] (eval at makeNodePromisifiedEval (/home/ireslab11/Desktop/node/node/node_modules/bluebird/js/release/promisify.js:184:12), :14:23)
at _bluebird.default.try (/home/ireslab11/Desktop/node/node/node_modules/bitcoin-core/dist/src/index.js:168:27)
at tryCatcher (/home/ireslab11/Desktop/node/node/node_modules/bluebird/js/release/util.js:16:23)
at Function.Promise.attempt.Promise.try (/home/ireslab11/Desktop/node/node/node_modules/bluebird/js/release/method.js:39:29)
at Client.command (/home/ireslab11/Desktop/node/node/node_modules/bitcoin-core/dist/src/index.js:154:33)
at apply (/home/ireslab11/Desktop/node/node/node_modules/lodash/lodash.js:495:27)
at Client.wrapper [as getInfo] (/home/ireslab11/Desktop/node/node/node_modules/lodash/lodash.js:5356:16)

Stop using deprecated "getinfo" RPC

Optional geo-location map for peers

Annotate interesting historical events

Ref: https://en.bitcoin.it/wiki/Bitcoin_Firsts

plotting the chart

good work and keep it coming wondering if there is a way to plot chart with RPC and php array data, would be an amazing addon to yours explorer

Add support for disconnecting RPC and reconnecting with different params

Required same tool for bitcoin cash

hi janoside,

I am looking tool for bitcoin cash

Identify miners for blocks

https://github.com/blockchain/Blockchain-Known-Pools

Mempool Info page blank

Any ideas why?

https://i.gyazo.com/6823bb120316167c56dea911c0fe5fec.png

Display more detailed errors in situations like #45

Like #45

Does this project support bitcoin-abc?

if not, it will?

Show mempool "time" for unconfirmed transactions

Better validation of RPC commands when checking blacklist

Add docker support

It will be nice to have a docker image for this repository

bech32 addresses don't wrap and overrun the horizontal space allotted

See https://btc-explorer.com/tx/2143c53089bceb1b94eea7326de499e2d6d4056551048989d88b7ed3a02c3809

Add support for displaying values in bits

Clean up dependencies

There are a bunch of unused dependencies that should be removed.

Search by address

Hey janoside,

thank you for the nice explorer! I modified it to support another coin and search by block id, block hash, and transaction hash works well. Also, block 0 gets displayed without problems.

I only run into problems when I search by address. Do I need to modify any other value to get this working?

Invalid query: ihgcntcbzgkvfuwfkvq7ghzpzmp26uyscs

Greetings,
Chris