Frequently Asked Questions about our explorers and service.
If you do not agree with our Terms, promptly exit this page without accessing or using any of the services.
A wallet can have multiple addresses, and you can have so-called "change addresses"
(see https://en.bitcoin.it/wiki/Change) which
will be generated automatically whenever you spend less than you have.
Those "change addresses" are part of the Bitcoin (and alt-coins) anonymity features, are known only to your wallet and can hold more than small change.
They are not displayed in the usual wallet UI, but you can typically view them by going to the debug console and typing "listunspent".
Our explorers can sometime guess those addresses, but not all the time, and only ofter after the fact. When that happens an address will be aggregated in a "guesstimated wallet".
Guesstimated wallets are a unique and experimental feature of our explorers.
The "guesstimation" involves a taint analysis on the blockchain transactions, and tries to guess which addresses are (or were) part of a given user wallet, to provide a more accurate rich list.
The way taint is accumulated by a blockchain is quite random, and usually is not significant for individual's wallets, however Exchanges and major processors can naturally accumulate a lot of taint over time, so their guesstimated wallets can be meaningful.
Even in the best of cases, guesstimated wallets are an underestimation of a wallet balance, the actual balance of a wallet is at least what was guesstimated, and usually higher.
Outstanding coins are computed from the transaction outputs, with sometimes burn addresses being zero'ed (by request, and for publicly documented burns).
The differences usually come from two sources:
Currently they are updated every 6 hours, there is no set time at which the updates happen, it is different for every explorer to spread the workload.
Those addresses are the temporary naming scheme we use for segregated witness outputs, as no standard has yet been established (most advanced proposal seems to be BIP-0173, but it is still a draft.
We hope that this situation will be resolved soon, and the chosen name scheme will be implemented in the respective RPC APIs, so that how segwit "stuff" is named becomes an unambiguous standard for each blockchain.
There are three MPOS parameters to configure, for chain xyz the parameters will be:
Note: Explorer additions are currently suspended
After a hectic early 2017, we are reaching the limits of our current infrastructure, back-office tools especially. So rather than jeopardizing stability of current explorers, we are suspending addition of new explorer for Summer 2017, and we will use that time to upgrade our back-office and automation tools.
We require a client wallet with a Bitcoin-compatible RPC API, that can be compiled from source code (preferably on github or similar) and that will run under Debian 7
We may also currently ask for a contribution to hosting costs, as servers
hosting the wallet daemons are our major source of expenses.
Currently, we prefer to host the daemon ourselves for reliability reason, both so we know what code the daemon is running and to ensure good uptime.
Preferred contact method is currently through bitcointalk.
Note that due to unclear BitLicense requirements, requesting an explorer is not possible for New York state residents or citizens. If you happen to live or be a New York state citizen, please contact the NY DFS for further inquiries.
All Explorers come with the standard feature set:
Explorers and nodes are also monitored, and a backup server is maintained ready.
The explorers are built on alternative tech, not related to abe, insight or other existing explorers.
The server-side code is powered by DWScript
and SQLite databases, and was initially
built as a tech demonstrator.
The client-side makes use of jQuery, Bootstrap, Google Charts and jqGeoChart
Wallets are hosted on Ubuntu 14 and 16 (LTS) servers.