bitcoin_2013_blockhash.csv.gz -- enumeration of all blocks in the blockchain, 277443 rows, 4 columns: blockID - id used in this dataset (starts from 0, continous, ordered) bhash - block hash (identifier in the blockchain, 64 hex characters) btime - creation time (from the blockchain); note: block timestamps are NOT ordered (they are based on the local time of the miner which does vary) txs - number of transactions bitcoin_2013_txhash.csv.gz -- transaction ID and hash pairs, 30048983 rows, 2 columns: txID - id used in this dataset (starts from 0, continous, ordered) txhash - transaction hash used in the blockchain (64 hex characters) bitcoin_2013_addresses.csv.xz -- Bitcoin address IDs, 24618959 rows, 2 columns: addrID - id used in this dataset (starts from 0, not continuous, ordered the address with addrID == 0 is invalid /blank, not used/) addr - string representation of the address (alphanumeric, maximum 35 characters; note that the IDs are NOT ordered by the addr) bitcoin_2013_tx.csv.xz -- enumaration of all transactions, 30048983 rows, 4 columns: txID - transaction ID (from the txhash.txt file), ordered blockID - block ID (from the blockhash.txt file), ordered n_inputs - number of inputs n_outputs - number of outputs bitcoin_2013_txin.txt.xz -- list of all transaction inputs (sums sent by the users), 65714232 rows, 3 columns: txID - transaction ID (from the txhash.csv file), ordered addrID - sending address (from the addresses.csv file) value - sum in Satoshis (1e-8 BTC -- note that the value can be over 2^32, use 64-bit integers when parsing) bitcoin_2013_txout.txt list of all transaction outputs (sums received by the users), 73738345 rows, 3 columns: txID - transaction ID (from the txhash.csv file), ordered addrID - receiving address (from the addresses.csv file) value - sum in Satoshis (1e-8 BTC -- note that the value can be over 2^32, use 64-bit integers when parsing) contraction1.csv.xz -- list of addresses possibly belonging to the same entity after 235,000 blocks (corresponding to the network analyzed in the PLOS ONE article https://doi.org/10.1371/journal.pone.0086197), 13086528 rows, 2 columns: addrID - address ID (from the addresses.csv file) userID - ID of identified entity (not continuos, each two addrID which belong to the same "entity" appear as inputs in the same transaction at least once); this file is sorted by (userID, addrID) contraction2.csv.xz -- list of addresses possibly belonging to the same entity, after 277,443 blocks (corresponding to the network analyzed in the NJP article https://doi.org/10.1088/1367-2630/16/12/125003), 24618959 rows, 2 columns: addrID - address ID (from the addresses.csv file) userID - ID of identified entity (not continuos, each two addrID which belong to the same "entity" appear as inputs in the same transaction at least once); this file is sorted by (userID, addrID) balances.csv.xz -- balances of nodes at specific times, 64360175 rows, 3 columns: blockID - ID of block after this balance was calculated (potential values: 100000, 120000, 140000, 160000, 180000, 199956, 228931, 234999, 277442) addrID - address ID (from the addresses.csv file); this file is sorted by (blockID, addrID) balance - balance in Satoshis (1e-8 BTC -- note that the value can be over 2^32, use 64-bit integers when parsing) degree.csv.xz -- node degrees (number of distinct transaction partners), after 277,443 blocks, 24575385 rows, 3 columns: addrID - address ID (from the addresses.csv file), ordered indeg - indegree (number of distinct addresses which appear as inputs in transactions where this address appears as output) outdeg - outdegree (number of distinct addresses which appear as outputs in transactions where this address appears as input) txedge.csv.xz -- edges constructed from the transactions: a transaction with 2 inputs and 3 outputs results in 6 edges (all possible combinations), an edge may appear multiple times, with the corresponding transaction IDs, 129178908 / 361759010 rows, 3 columns: txID - transaction ID in which this edge appears, ordered addrin - sending address ID (corresponds to addrID in addresses.csv) addrout - receiving address ID (corresponds to addrID in addresses.csv) txedgeunique.csv.xz -- edges constructed from the transactions, list of unique edges after 277,443 blocks; each edge appears only once, 89220163 / 294484230 rows, 2 columns: addrin - sending address ID (corresponds to addrID in addresses.csv) addrout - receiving address ID (corresponds to addrID in addresses.csv); note: this file is sorted by (addrout, addrin)