Try Quests to earn cryptoTokenflow Trailblazers
Q1. Dive into the Tokenflow data and tell us what you find. Conduct a brief analysis on a topic of your choice, with at least 1 data visualization and a succinct paragraph describing your findings. Additionally, share your experience with the data: was anything missing that you expected to find, were there difficulties you encountered, was there documentation you desired, etc? How does this data change the way you think about and analyze Ethereum data?
Introducing some columns of the Transactions table
In order to ensure the correct order of transactions in the blockchain, each block contains the hash (a hash is the result of mapping a block of data into data of fixed size using a cryptographic function) of the previous block, as shown in Figure below.
Methodology
In this dashboard, we examined the Transactions table for the tokenflow_eth database. In the following, we will introduce and review some columns of the transactions table. In the next step, we go to a desired topic and analyze it. Finally, we describe our user experience of using the tokenflow_eth database.
Using tokenflow_eth database, 5 hash blocks have been obtained for a desired address.
Information about an arbitrary block is extracted using the tokenflow_eth Database.
The name of the block column in the Ethereum database is block_id.
A txid or Transaction ID is a string of letters and numbers that identifies a specific transaction on the blockchain. The string is simply the double SHA-256 hash of a transaction. This hash can be used to look up a transaction on a node or block explorer.
>> Refrence: river.com/learn
>> Refrence: https://ethereum.org/en/developers/docs/blocks/
There is a column in the tokenflow_eth Database called TX_HASH. This column in the Ethereum database is called TX_ID. In the following, we found information about a custom Tx Id from the tokenflow_eth database & Ethereum database.
In this section, only three columns of the transactions table from the tokenflow_eth database were introduced to show a simple experience of using this database and to briefly explain some of the main concepts of blockchain.
Our chosen topic
In this section, we have considered the Bentobox address on the Ethereum chain and examined its activity from different aspects. All information and charts are extracted from the tokenflow_eth database.
The chart below shows the number of transactions performed daily to the Bentobox address.
According to the above diagram, the following information is extracted:
- The highest number of transactions to Bentobox was recorded on March 26, 2021.
- The maximum number of transactions to Bentobox was equal to 346 transactions.
- The lowest number of transactions to Bentobox was recorded on April 7, 2021.
- The minimum number of transactions to Bentobox is equal to 2 transactions.
- An average of 28 transactions have been made to Bentobox address daily.
The total number of transactions made to Bentbox is equal to:
Some of the above transactions have failed. Percentage of successful and failed transactions is equal to:
According to the chart above, about 97% of the transactions sent to the Bentbox address were successful.
Our user experience
- For analysts who always use Atrium database tables, they may be confused at first when using the tokenflow_eth database, as some columns in the tokenflow_eth database are listed under different names than the Atrium database.
- In some cases, irrelevant errors occurred while such an error did not exist. Of course, this could also be one of the user's mistakes.
- Obviously, the tokenflow_eth database still has a lot of room for improvement compared to the Atrium database!