Summary API

You can obtain summary information about all our explorers at the following URL :

https://chainz.cryptoid.info/explorer/api.dws?q=summary

It returns a short summary of all our explorer. You can also use '24summary' which includes min/max/median for various blocks and transactions for the last 24 hours.

API Calls Root URL for explorers

API shares a normalized root URL which is:

https://chainz.cryptoid.info/coin/api.dws

So for instance the url root for Riecoin (ric) will be "https://chainz.cryptoid.info/ric/api.dws".

Query API

The API function to call is specified through the q parameter.
For instance you can ask the current difficulty of Riecoin with "https://chainz.cryptoid.info/ric/api.dws?q=getdifficulty".

Real-Time Simple Queries

• addresses: returns a JSON object with the number of known and non-zero addresses (with funds)
• circulating: returns the number of circulating coins (minus reserve, Prime holdings... see noncirculating)
• getblockcount: returns the current block height as a plain text string
• getdifficulty: returns the difficulty as a plain text string
• hashrate: returns the hashrate in GH/s (when supported, blockchain.info API compatible)
• masternodecount: returns the number of masternodes, or "?" if unknown or non-applicable.
• masternodeinfo: returns a JSON with masternode and distinct servers count.
• nethashps: returns the hashrate in H/s (when supported)
• netmhashps: returns the hashrate in MH/s (when supported)
• nodes: returns a list of recently seen nodes, grouped by version (JSON format)
• noncirculating: returns the number of non-circulating coins (if any) that are tied in reserves, prime holdings, etc.
• rich: returns the rich list top 1000 (JSON format)
• summary: returns summary information for all explorers
• ticker.btc: returns the last market ticker in BTC, as tracked by the explorer, only one market is tracked and this value can be several minutes behind the market. Use market APIs directly for more accurate quotations.
• ticker.usd: returns the last market ticker in USD, as tracked by the explorer and BitPay rate, only one market is tracked and this value can be several minutes behind the market. Use market APIs directly for more accurate quotations.
• totalbc: returns the outstanding number of coins in satoshis (x 1e8, for compatibility with blockhain.info API)
• totalcoins: returns the outstanding number of coins

Address Queries

Pass the address in the a parameter.

• addressfirstseen: returns the date and time of the block in which the address was first seen, or a string begining with "ERROR:" otherwise.
• addressinfo: returns a JSON object with information about an address (balance, transaction count, first & last block...), or null if the address is unknown or invalid.
• getbalance: returns the balance of the address. For incorrect addresses or addresses never seen on the network, the returned balance is zero. Can be delayed by up to 6 hours unless you specify an API Key.
• getbalances: this API expects a POST with the content data being a JSON array of addresses (max length < 4kB), and returns a JSON object with the current balances of these addresses. An API key is required.
• getreceivedbyaddress: returns the amount received by the address (sum of vout). For incorrect addresses or addresses never seen on the network, the returned amount is zero. Can be delayed by up to 1 hour.
• richrank: returns the rich list rank for the address.

Block Queries

Block APIs only consider blocks in the "main" chain (as determined by the explorer wallet).

• getblockhash: takes a height parameter and returns corresponding block hash.
• getblockheight: takes a hash parameter and returns corresponding block height.
• getblocktime: takes a height parameter and returns unixtime of the block.

Transaction Queries

Pass the transaction hash in the t parameter.

• lasttxs: returns the last ten transactions (with at least one confirmation), excluding coinbase and stake transactions
• txinfo: returns summary information about a transaction (confirmations, fees, inputs & output addresses and amounts).

API Keys

API Keys can be requested for free, when passed to the API (in the key parameter) they lift some restrictions and give access to "live" data with no cache latencies.
API Keys are only used to protect more CPU intensive queries from potential abuse. An API Key is valid for all our explorers.

• getbalance returns the current value, with no delays.
• multiaddr becomes available, this API is similar to blockchain.info's, it has a single active parameter in which you can pass multiple addresses separated by '|'. It returns summary information about those addresses (balance, total sent/receive and latest transactions). By default returns the last 50 transactions, but this number can be adjusted by the optional n parameter.
• unspent becomes available, this API is similar to blockchain.info's, it has a single active parameter in which you can pass multiple addresses separated by '|'. It returns information about unspent outputs of those addresses.
• txbymessage becomes available, pass it an m parameter with the text to be searched in transaction messages (it uses full text search). It will return a list of recent transactions matching the search. You can optionally pass a before parameter with the block height (excluded) before which to search.
• allbalances becomes available for chains will less than 150k addresses holding funds, it returns the balance of all addresses that have a non-zero balance, with a worst latency of approx 5 minutes.

Undocumented APIs

The various pages of the site use "undocumented" APIs for their own purpose.
You are free to use them (use, not abuse!), but be aware they can change at any time without notice.