DOI: 10.5281/zenodo.4718440
title: Transaction Graph Dataset for the Ethereum Blockchain

description: This dataset contains ether as well as popular ERC20 token transfer transactions extracted from the Ethereum Mainnet blockchain. Only send ether, contract function call, contract deployment transactions are present in the dataset. Miner reward (static block reward) and "uncle block inclusion reward" are added as transactions to the dataset. Transaction fee reward and "uncles reward" are not currently included in the dataset. Details of the datasets are given below: <strong>FILENAME FORMAT:</strong> The filenames have the following format: eth-tx-&lt;start blockno&gt;-&lt;end blockno&gt;.txt.bz2 where &lt;start blockno&gt; is the starting block number and &lt;end blockno&gt; final block number. For example file eth-tx-1000000-1099999.txt.bz2 contains transactions from block 1000000 to block 1099999 inclusive. The files are compressed with bzip2. They can be uncompressed using command bunzip2. <strong>TRANSACTION FORMAT:</strong> Each line in a file corresponds to a transaction. The transaction has the following format: &lt;SYMBOL&gt; &lt;blockno&gt; &lt;tx no&gt; &lt;from addr&gt; &lt;to addr&gt; &lt;value&gt; &lt;SYMBOL&gt; is the abreviation for the asset. For example ETH means ether transfer in Wei units. ERC20 tokens transfers (transfer and transferFrom function calls in ERC20 contract) are indicated by token symbol. For example GUSD is Gemini USD stable coin. The JSON file erc20tokens.json given below contains the details of ERC20 tokens. Failed transactions are prefixed with "F-". &lt;blockno&gt; Number of the block which contains the transaction. &lt;tx no&gt; Position of the transaction in the block (i.e. transaction number in the block). Static block reward and uncle block inclusion reward has 0 as tx no. The position of transactions in the block is shifted by 1. The first transaction has 1 as tx no. &lt;from addr&gt; Source ethereum address of the transfer. For static block rewards, the from addr is ETHMAINBLOCK. For uncle block inclusion rewards, the from addr is ETHMAINUNCLE. &lt;to addr&gt; Destination ethereum address of the transfer. The to addr is 0x0 for contract deployment transactions instead of null. &lt;value&gt; Amount of transfer. The amount is given as hexadecimal a number. <strong>BLOCK TIME FORMAT:</strong> The block time file has the following format: &lt;block no&gt; &lt;timestamp&gt; &lt;block no&gt; Number of the block. &lt;timestamp&gt; Unix timestamp at which the block is mined as a hexadecimal number. <strong>erc20tokens.json FILE: </strong> This file contains the list of popular ERC20 token contracts whose transfer/transferFrom transactions appear in the data files. ERC20 token list: USDT TRYb XAUt BNB LEO LINK HT HEDG MKR CRO VEN INO PAX INB SNX REP MOF ZRX SXP OKB XIN OMG SAI HOT DAI EURS HPT BUSD USDC SUSD HDG QCAD PLUS BTCB WBTC cWBTC renBTC sBTC imBTC pBTC <strong>IMPORTANT NOTE:</strong> Public Ethereum Mainnet blockchain data is open and can be obtained by connecting as a node on the blockchain or by using the block explorer web sites such as http://etherscan.io . The downloaders and users of this dataset accept the full responsibility of using the data in GDPR compliant manner or any other regulations. We provide the data as is and we cannot be held responsible for anything. <strong>NOTE:</strong> If you use this dataset, please do not forget to add the DOI number to the citation. If you use our dataset in your research, please also cite our paper: https://link.springer.com/article/10.1007/s10586-021-03511-0 <pre><code>@article{kilic2022parallel, title={Parallel Analysis of Ethereum Blockchain Transaction Data using Cluster Computing}, journal={Cluster Computing}, author={K{\i}l{\i}{\c{c}}, Baran and {\"O}zturan, Can and Sen, Alper}, year={2022}, month={Jan} }</code></pre>
description: {"references": ["B. K\u0131l\u0131\u00e7, C. \u00d6zturan and A. Sen, \"A Cluster Based System for Analyzing Ethereum Blockchain Transaction Data,\" 2020 Second International Conference on Blockchain Computing and Applications (BCCA), 2020, pp. 59-65, doi: 10.1109/BCCA50787.2020.9274081."]}