Now you can request additional data and/or customized columns!

Try It Now!

Bitcoin

cryptocurrency

Files Size Format Created Updated License Source
2 4MB csv zip 2 years ago 1 year ago Open Data Commons Public Domain Dedication and License
Data sources and methodology Daily on-chain transaction volume is calculated as the sum of all transaction outputs belonging to the blocks mined on the given day. “Change” outputs are not included. Estimation difficulties remain and the measure is imprecise. We discuss this here. Methodology read more
Download Developers

Data Files

Download files in this dataset

File Description Size Last changed Download
bitcoin 434kB csv (434kB) , json (1MB)
bitcoin_zip Compressed versions of dataset. Includes normalized CSV and JSON data with original data and datapackage.json. 572kB zip (572kB)

bitcoin  

Signup to Premium Service for additional or customised data - Get Started

This is a preview version. There might be more data in the original version.

Field information

Field Name Order Type (Format) Description
date 1 date (%Y-%m-%d)
txVolume(USD) 2 string (default)
adjustedTxVolume(USD) 3 string (default)
txCount 4 integer (default)
marketcap(USD) 5 string (default)
price(USD) 6 string (default)
exchangeVolume(USD) 7 string (default)
generatedCoins 8 number (default)
fees 9 number (default)
activeAddresses 10 integer (default)
averageDifficulty 11 number (default)
paymentCount 12 any (default)
medianTxValue(USD) 13 string (default)
medianFee 14 any (default)
blockSize 15 integer (default)
blockCount 16 integer (default)

Integrate this dataset into your favourite tool

Use our data-cli tool designed for data wranglers:

data get https://datahub.io/cryptocurrency/bitcoin
data info cryptocurrency/bitcoin
tree cryptocurrency/bitcoin
# Get a list of dataset's resources
curl -L -s https://datahub.io/cryptocurrency/bitcoin/datapackage.json | grep path

# Get resources

curl -L https://datahub.io/cryptocurrency/bitcoin/r/0.csv

curl -L https://datahub.io/cryptocurrency/bitcoin/r/1.zip

If you are using R here's how to get the data you want quickly loaded:

install.packages("jsonlite", repos="https://cran.rstudio.com/")
library("jsonlite")

json_file <- 'https://datahub.io/cryptocurrency/bitcoin/datapackage.json'
json_data <- fromJSON(paste(readLines(json_file), collapse=""))

# get list of all resources:
print(json_data$resources$name)

# print all tabular data(if exists any)
for(i in 1:length(json_data$resources$datahub$type)){
  if(json_data$resources$datahub$type[i]=='derived/csv'){
    path_to_file = json_data$resources$path[i]
    data <- read.csv(url(path_to_file))
    print(data)
  }
}

Note: You might need to run the script with root permissions if you are running on Linux machine

Install the Frictionless Data data package library and the pandas itself:

pip install datapackage
pip install pandas

Now you can use the datapackage in the Pandas:

import datapackage
import pandas as pd

data_url = 'https://datahub.io/cryptocurrency/bitcoin/datapackage.json'

# to load Data Package into storage
package = datapackage.Package(data_url)

# to load only tabular data
resources = package.resources
for resource in resources:
    if resource.tabular:
        data = pd.read_csv(resource.descriptor['path'])
        print (data)

For Python, first install the `datapackage` library (all the datasets on DataHub are Data Packages):

pip install datapackage

To get Data Package into your Python environment, run following code:

from datapackage import Package

package = Package('https://datahub.io/cryptocurrency/bitcoin/datapackage.json')

# print list of all resources:
print(package.resource_names)

# print processed tabular data (if exists any)
for resource in package.resources:
    if resource.descriptor['datahub']['type'] == 'derived/csv':
        print(resource.read())

If you are using JavaScript, please, follow instructions below:

Install data.js module using npm:

  $ npm install data.js

Once the package is installed, use the following code snippet:

const {Dataset} = require('data.js')

const path = 'https://datahub.io/cryptocurrency/bitcoin/datapackage.json'

// We're using self-invoking function here as we want to use async-await syntax:
;(async () => {
  const dataset = await Dataset.load(path)
  // get list of all resources:
  for (const id in dataset.resources) {
    console.log(dataset.resources[id]._descriptor.name)
  }
  // get all tabular data(if exists any)
  for (const id in dataset.resources) {
    if (dataset.resources[id]._descriptor.format === "csv") {
      const file = dataset.resources[id]
      // Get a raw stream
      const stream = await file.stream()
      // entire file as a buffer (be careful with large files!)
      const buffer = await file.buffer
      // print data
      stream.pipe(process.stdout)
    }
  }
})()

Read me

Data sources and methodology

Daily on-chain transaction volume is calculated as the sum of all transaction outputs belonging to the blocks mined on the given day. “Change” outputs are not included. Estimation difficulties remain and the measure is imprecise. We discuss this here. Methodology behind adjusted transaction volume figures is described in this post.

Transaction count figure doesn’t include coinbase and coinstake transactions.

Active addresses is the number of unique sending and receiving addresses participating in transactions on the given day.

Payment count for UTXO coins is defined as sum of outputs’ count minus one for each transaction. We assume that transaction with N outputs pays to N – 1 addresses and the last N-th output is change. Transactions with only one output do not contribute to payment count, as they are likely to be a self-churn. Payment count for smart contract assets such as ETH or LSK is calculated as the amount of transfer transactions (i.e. contract creation, invocation, destruction transactions are not included).

NEO and GAS transaction count figures reflect the amount of transactions that have at least one output of given asset type. If transaction sends both NEO and GAS, it will be included in transaction count for both assets. Fees figure is denominated in GAS and calculated by summing the fees of all transactions that have at least one output of a given asset type.

Ripple data includes only transactions of Payment type that transfer XRP tokens.

Stellar transaction volume data covers only operations of Payment and CreateAccount types that transfer XLM tokens. Transaction count is the number of transactions that include at least one operation of aforementioned types. Lumens inflation data is currently unavailable.

XEM data includes only transactions of “Transfer” type.

Zcash figures for on-chain volume and transaction count reflect data collected for transparent transactions only. In the last month, 9.1% (14/06/18) of ZEC transactions were shielded, and these are excluded from the analysis due to their private nature. Thus transaction volume figures in reality are higher than the estimate presented here, and NVT and exchange to transaction value lower. Data on shielded and transparent transactions can be found here and here.

Monero transaction volume is impossible to calculate due to RingCT which hides transaction amounts.

EOS transaction volume figure includes only transactions of transfer type. Median transaction value for EOS is actually median transfer value (currently, most transactions in EOS do not transfer EOS token).

WAVES transaction volume figure includes only transactions of transfer and mass transfer types. Median transaction value for WAVES is actually median value of WAVES token transfer.

Price data All coins: coinmarketcap.com

On-chain transaction volume data BTC, BCH, LTC, DCR, DASH, ZEC, DOGE, PIVX, XVG, VTC, DGB, BTG, USDT, MAID: data collected from blockchains and aggregated by CM Python tools ETH and ERC20 tokens, ETC, XMR, XEM, ADA, LSK, NEO, GAS: data collected from blockchains by CM Haskell tools and aggregated by companion analytics scripts XRP: data collected from data.ripple.com by CM Haskell tools and aggregated by companion analytics scripts XLM: data collected from history.stellar.org by CM Haskell tools and aggregated by companion analytics scripts Coinmetrics is a data aggregator and visualization service. Any written content is opinion, and should be used for informational purposes only. Content on this website is not intended to and does not constitute investment advice. Seek a licensed professional for investment advice.

Fields

txVolume(USD) - on-chain transaction volume. A broad and largely unadjusted measure of the total value of outputs on the blockchain, on a given day. This is an answer to the question “approximately how much value, denominated in USD, circulates on the Bitcoin blockchain a day?”

That said, on-chain transaction volume in practice is a very hard thing to estimate properly. We discuss that at length in this post. Please read it! We don’t want to give anyone a false degree of certainty in the number. We are currently working through various methods to improve the estimate, and maybe get closer to blockchain.info’s adjusted figure – but that will take time. So bear with us.

txCount - refers to the number of transactions happening on the public blockchain a day. Be aware that for low-fee blockchains, it’s really easy to fabricate a whole bunch of transactions. So this isn’t necessarily that reliable! Additionally, UTXO networks like Bitcoin can batch a whole bunch of transactions into one, so txCount underestimates those ones. You have to therefore be careful comparing the number of transactions on Ethereum with Bitcoin; by its very nature, Bitcoin typically has more transactions than that datapoint suggests. Naively comparing the UTXO to account based systems by transaction count is like watching motorway traffic and comparing the number of buses versus motorcycles to guess at how many people are making trips. Maybe there are the same number of buses and motorcycles – but each bus might have 50 people inside of it.

Here’s a very typical example of a batched Bitcoin transaction. One sender, lots of receivers.

bitcoin-transaction

This is fairly typical for Bitcoin. Maybe it’s a mining pool paying out, or an exchange paying multiple users at once. Batching transactions saves space, and is more cost-efficient, so it’s encouraged. It also means that just counting transactions for Bitcoin (or other UTXO chains) isn’t likely to yield a reliable estimate of how many actual transactions are occurring. The useful site outputs.today popped up recently to make this point. Of course, outputs.today might be including change outputs (we’re not sure if they are or not), which aren’t meaningful transfers. But even if you conservatively assumed that half of all bitcoin outputs tallied on outputs.today are change outputs, you would still have a higher number of outputs than just the raw number of transactions. So please be aware of the fact that Bitcoin transactions have the flexibility of email (one can send to many), constrained only by the blocksize and the willingness of miners to include large transactions.

marketcap(USD) - This is the unit price multiplied by the number of units in circulation. There has been quite a bit of controversy over this indicator. We still like this post from the Sia guys on the topic. Marketcap or network value is definitely flawed. It becomes less tethered to reality the smaller the float is. Float means the ratio of actual circulating units to the total number of units. Ripple, for instance, has a fairly small float, so one should probably be skeptical of its “market cap.” OnChainFx is doing a lot of good work on the issue.

Price - not much to say about this one. We get it from CoinMarketCap, with all the caveats that entails. Be advised – it’s the opening price.

exchangevolume(USD) is, as you might expect, the dollar value of the volume at exchanges like GDAX and Bitfinex. We get this data to Coinmarketcap, who have a bit of a conflicted history with the figure, having deleted and re-added Korean exchange figures. It doesn’t include data on OTC exchanges, which is a meaningful portion of all global exchange. Remember that 0-fee exchange volume should be taken with a grain of salt.

generatedCoins - this refers to the number of new coins that have been brought into existence on that day. We count up the actual number of newly-minted coins, rather than using the stated inflation figures (i.e. for bitcoin you should expect 12.5 per block, every ten minutes, giving you 12.5624 = 1800 coins per day). You can see that we’ve been exceeding 1800 coins per day recently – this is due to lots of new hashpower which is coming online and making blocks come every 8 or 9 minutes than 10. In practice, since hashpower is continually added to the system, Bitcoin inflation progresses slightly faster than its theoretical rate. This is also why our figures differ from those of other websites – we count up the actual number of new coins rather than just assuming the official inflation rates are correct.

Fees - Fees in our data are based on the native currency, not USD. So on January 28th, fees totaled 168.25 BTC. That’s about $1.88m. This has been a source of confusion for many, so again – fees are counted in the native currency. You have to multiply by unit price to obtain the USD value of fees. Fees are interesting because they can’t really be faked – either you want to use the blockchain, and you’ll pay to do it, or you choose not to.

averaDifficulty - average measure of how difficult it is to find a hash below a given target. The Bitcoin network has a global block difficulty. Valid blocks must have a hash below this target. Mining pools also have a pool-specific share difficulty setting a lower limit for shares.

So to conclude, on-chain volume and transaction count can both be faked and can be tricky to estimate. Exchange volume must be viewed fairly skeptically. Market cap has a whole host of methodological issues. Generated coins and fees, however, are much more concrete.

We hope this helps you assess our data. Do not take it as gospel – use it only with the appropriate dose of skepticism.

Datapackage.json

Request Customized Data


Notifications of data updates and schema changes

Warranty / guaranteed updates

Workflow integration (e.g. Python packages, NPM packages)

Customized data (e.g. you need different or additional data)

Or suggest your own feature from the link below