Главная » Криптовалюты

Bitcoin block explorer github

Содержание
  1. Bitcoin block explorer github
  2. Bitcoin block explorer github
  3. Bitcoin block explorer github
  4. About
  5. Bitcoin block explorer github
  6. Bitcoin block explorer github

Bitcoin block explorer github

Simple, database-free Bitcoin base blockchain explorer, via RPC. Built with Node.js, express, bootstrap-v4.

This tool is intended to be a simple, self-hosted explorer for the Bitcoin base blockchain, driven by RPC calls to your own coind node. This tool is easy to run but currently lacks features compared to database-backed explorers.

Whatever reasons one might have for running a full node (trustlessness, technical curiosity, supporting the network, etc) it’s helpful to appreciate the «fullness» of your node. With this explorer, you can not only explore the blockchain (in the traditional sense of the term «explorer»), but also explore the functional capabilities of your own node.

  • Browse blocks
  • View block details
  • View transaction details, with navigation «backward» via spent transaction outputs
  • View JSON content used to generate most pages
  • Search by transaction ID, block hash/height, and address
  • Optional transaction history for addresses by querying from ElectrumX, blockchain.com, blockchair.com, or blockcypher.com
  • Mempool summary, with fee, size, and age breakdowns
  • RPC command browser and terminal

Changelog / Release notes

The below instructions are geared toward BTC, but can be adapted easily to other coins.

These steps are for bitcoin but other supported bitcoins base coin should have similar setup

  1. Install and run a full, archiving node — instructions. Ensure that your bitcoin node has full transaction indexing enabled ( txindex=1 ) and the RPC server enabled ( server=1 ).
  2. Synchronize your node with the Bitcoin network.
  3. «Recent» version of Node.js (8+ recommended).

If you’re running on mainnet with the default datadir and port, this Should Just Work. Open http://127.0.0.1:3002/ to view the explorer.

You may set configuration options in a .env file or using CLI args. See configuration for details.

Configuration options may be passed as environment variables or by creating an env file at

/.config/btc-rpc-explorer.env or at .env in the working directory. See .env-sample for a list of the options and details for formatting .env .

You may also pass options as CLI arguments, for example:

See rpc-explorer —help for the full list of CLI options.

Источник

Bitcoin block explorer github

Bitcoin Block Explorer

Hey! So, I’m all out of time to commit here, so this will have to remain imperfect, but I’m still fairly happy with the results. It’s a working Bitcoin block explorer, where you can browse from block to block and view the transactions.

Things that still need work:

    1. Block Search: Currently crippled by the CORS policy on the APIs I’ve tried. Need to tinker with proxies to bypass that, or make my own API layer to fetch the BTC data (real world would probably do that). No time now so it remains broken. Please inspect src/agent.js and src/components/Header.js to see that it would/should work otherwise. Just needs the CORS policy.
    1. Styling: Obviously this is not a killer app. Ain’t the prettiest. Needs some more perfecting, but that takes time. Should organize the block data in a prettier way, maybe go two-column or group data up differently. Maybe generate pictures from hashes. Animations, etc. Popup tooltips. TODO.
    1. Transactions pagination: Again, needs more styling for buttons etc, but it’s currently fully working. Would probably use AwesomeFont icons or whatnot, but opted not to open up the external library can of worms right now.
    1. Misc functionality: Plenty more that could be done here, obviously. Search by hash/height/transaction-hash, transaction input/outputs, wallets tracking, summing fees from all transactions per block, etc. Performance could be improved too — need to be able to preload some blocks so each one doesn’t have a load delay. Need to solve CORS issue for that though (or make clever batch crawler). Show/hide transactions by clicking header.
    1. Odd Decisions: e.g. I like using the long hashes as header/footers to a block, so the Merkle Root is a footer now. Kinda works. Should probably be ellipsis shortened with a «Copy to Clipboard» icon instead though, long term. Oh well.
    1. Tests. Though I follow Jonathan Blow and John Carmack in advocating we make those very low priority vs integration tests and just general development — the code bloat is real otherwise, makes changing your API/namespace/structure etc very unwieldy. That’s just the tl;dr argument though.
Читайте также:  Asus rog strix scar g533qm hf030 майнинг

Anyway! Enjoy this limited-time snapshot of what I can do in a bit over a day and a half. Hopefully overkill, hopefully not underkill, most likely somewhere in-between! Really hope to work with you guys. I love the BTC space, spent a good year where all my free time went into researching ETH/Dfinity/Bancor/EOS/etc, and still always keeping an eye out through the Insiders Trading Group on Discord for the major twists and turns of the industry. Strongly believe decentralized crypto tech is the future, and would love to grow my career further into the space. Cheers.

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Note: this is a one-way operation. Once you eject , you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject . The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

To learn React, check out the React documentation.

Источник

Bitcoin block explorer github

BTC RPC Explorer

Читайте также:  Внутренняя норма доходности это отношение

Simple, database-free Bitcoin blockchain explorer, via RPC. Built with Node.js, express, bootstrap-v4.

This tool is intended to be a simple, self-hosted explorer for the Bitcoin blockchain, driven by RPC calls to your own bitcoind node. This tool is easy to run but currently lacks features compared to database-backed explorers.

I built this tool because I wanted to use it myself. Whatever reasons one might have for running a full node (trustlessness, technical curiosity, supporting the network, etc) it’s helpful to appreciate the «fullness» of your node. With this explorer, you can not only explore the blockchain (in the traditional sense of the term «explorer»), but also explore the functional capabilities of your own node.

Live demos are available at:

  • Browse blocks
  • View block details
  • View transaction details, with navigation «backward» via spent transaction outputs
  • View JSON content used to generate most pages
  • Search by transaction ID, block hash/height, and address
  • Optional transaction history for addresses by querying configurable ElectrumX servers
  • Mempool summary, with fee, size, and age breakdowns
  • RPC command browser and terminal
  • Currently supports BTC, LTC (support for any Bitcoin-RPC-protocol-compliant coin can be added easily)

The below instructions are geared toward BTC, but can be adapted easily to other coins.

  1. Install and run a full, archiving node — instructions. Ensure that your bitcoin node has full transaction indexing enabled ( txindex=1 ) and the RPC server enabled ( server=1 ).
  2. Synchronize your node with the Bitcoin network.
  3. «Recent» version of Node.js (8+ recommended).

If you’re running on mainnet with the default datadir and port, this Should Just Work. Open http://127.0.0.1:3002/ to view the explorer.

You may set configuration options in a .env file or using CLI args. See configuration for details.

Configuration options may be passed as environment variables or by creating an env file at

/.config/btc-rpc-explorer.env or at .env in the working directory. See .env-sample for a list of the options and details for formatting .env .

You may also pass options as CLI arguments, for example:

See btc-rpc-explorer —help for the full list of CLI options.

  1. docker build -t btc-rpc-explorer .
  2. docker run -p 3002:3002 -it btc-rpc-explorer

About

Public block explorer offered by Horizontal Systems for Bitcoin and Bitcoin Cash blockchains.

Источник

Bitcoin block explorer github

BCH RPC Explorer

Simple, database-free Bitcoin Cash blockchain explorer, via RPC. Built with Node.js, express, bootstrap-v4.

This tool is intended to be a simple, self-hosted explorer for the Bitcoin blockchain, driven by RPC calls to your own bitcoind node. This tool is easy to run but currently lacks features compared to database-backed explorers.

Whatever reasons one might have for running a full node (trustlessness, technical curiosity, supporting the network, etc) it’s helpful to appreciate the «fullness» of your node. With this explorer, you can not only explore the blockchain (in the traditional sense of the term «explorer»), but also explore the functional capabilities of your own node.

  • Network Summary «dashboard»
  • View details of blocks, transactions, and addresses
  • Analysis tools for viewing stats on blocks, transactions, and miner activity
  • View JSON content used to generate most pages
  • Search by transaction ID, block hash/height, and address
  • Optional transaction history for addresses by querying from ElectrumX and blockchair.com
  • Mempool summary, with fee, size, and age breakdowns
  • RPC command browser and terminal

Changelog / Release notes

Читайте также:  Данные по доходности ценных бумаг

The below instructions are geared toward BCH, but can be adapted easily to other coins.

  1. Install and run a full, archiving node — instructions. Ensure that your bitcoin node has full transaction indexing enabled ( txindex=1 ) and the RPC server enabled ( server=1 ).
  2. Synchronize your node with the Bitcoin network.
  3. «Recent» version of Node.js (8+ recommended).
  4. You could also run an ElectrsCash and configure the explorer to received data from it

If you’re running on mainnet with the default datadir and port, this Should Just Work. Open http://127.0.0.1:3002/ to view the explorer.

You may set configuration options in a .env file or using CLI args. See configuration for details.

Configuration options may be passed as environment variables or by creating an env file at

/.config/bch-rpc-explorer.env or at .env in the working directory. See .env-sample for a list of the options and details for formatting .env .

You may also pass options as CLI arguments, for example:

See bch-rpc-explorer —help for the full list of CLI options.

Источник

Bitcoin block explorer github

C4 Block explorer

Bitcoin/Altcoin block explorer (unfinished)

An attempt to write a blockexplorer with an insight explorer compatible API.
Unfinished explorer and needs a lot of refactoring since it was my first attempt to write a Golang application.

  • Go 1.10 or 1.11
  • Linux
  • MongoDB
  • dep https://github.com/golang/dep
  • btc or altcoin wallet with RPC ports etc configured.

example config: cat

and in config/app.yml

Installation instructions can be found here: https://golang.org/doc/install. It is recommended to add $GOPATH/bin to your PATH at this point.

To create the database for the block explorer use

or build the binary with

or build a binary with

Make sure the core wallet for the asset is running with the right RPC auth details
and make sure mongodb is running before you start.

  • Solving Reorgs (priority)
  • Complete frontend with Vuejs
  • Adress validation
  • Subsidy calculation for different coins instead of only viacoin
  • API endpoint block raw
  • Mempool unconfirmed transactions
  • API block summaries
  • API address properties
  • API query multiple addresses
  • Transaction broadcasting
  • Access mogodbd from remote host (assumes localhost now)
  • Support Postgresql too instead of Mongodb only

The timestamp property will only be set for unconfirmed transactions and height can be used for determining block order. The confirmationsFromCache is nolonger set or necessary, confirmation count is only cached for the time between blocks.

There is a new GET endpoint or raw blocks at /rawblock/ :

There are a few changes to the GET endpoint for /addr/[:address] :

  • The list of txids in an address summary does not include orphaned transactions
  • The txids will be sorted in block order
  • The list of txids will be limited at 1000 txids
  • There are two new query options «from» and «to» for pagination of the txids (e.g. /addr/[:address]?from=1000&to=2000 )

Some additional general notes:

  • The transaction history for an address will be sorted in block order
  • The response for the /sync endpoint does not include startTs and endTs as the sync is no longer relevant as indexes are built in bitcoind.
  • The endpoint for /peer is no longer relevant connection to bitcoind is via ZMQ.
  • /tx endpoint results will now include block height, and spentTx related fields will be set to null if unspent.
  • /block endpoint results does not include confirmations and will include poolInfo .

Источник

Оцените статью
© 2024 Идеи для бизнеса