Blockchain, first of all, is a technology and its implementation can vary greatly depending on what global problem a certain ecosystem is trying to solve. Some blockchains are trying to focus on performance to potentially replace traditional infrastructure (for example, VISA can process 12,000 transactions per second), while others put privacy as a main component of financial infrastructure. Yes, globally, at the heart of any blockchain are blocks that have certain storage capacities and, when filled, are closed and linked to the previously filled block, forming a chain of data known as the blockchain, but the storage organization itself can be radically different between blockchains. All business logic in Ethereum is mainly implemented through smart contracts, when, for example, in Polkadot, the implementation is done through pallets. Yes, even dwelling on the same smart contracts and comparing, for example, Ethereum and Solana. Firstly, they are written in different programming languages ( Solidity in the case of Ethereum, RUST | C | C++ in the case of Solana), and secondly, they implement completely different approaches to storage.

The bytecode is decoded and kept in raw form. The raw data that a certain blockchain is holding should be known to you if you have ever used a block explorer. These details differ amongst chains. However, as an illustration, the majority of chains powered by the Ethereum Virtual Machine (EVM) include:

These details differ amongst chains. However, as an illustration, the majority of chains powered by the Ethereum Virtual Machine (EVM) include:

• Blocks - groups of transactions appended to the chain

• Transactions - cryptographically signed blockchain state instructions

• Logs - events created by smart contracts

• Traces - step-by-step record of what happened during the execution of a transaction

In actuality, the aforementioned entities make up the entirety of the blockchain. This indicates that by using them alone, any decentralized ecosystem may already be fully analyzed. Although the data in these tables may be read by humans (unlike bytecode), doing so needs a deep understanding of blockchain.

Footprint Analytics supports raw data , allowing us to perform the analysis based on it.

You can access data from our web application by clicking Create -> New chart.

We store raw data in different tables, the name of which was built according to the following naming convention:

[chain]_[entity]

,where [chain] _is the name of the chain and [entity]_, on raw chain data example, is anything from the list we mentioned above (blocks, transactions etc.). To find the tables that are related to raw data for the specific chain one 1. enter its name in the sidebar and 2. select bronze level, as shown on the next screenshot.

As it could be seen, only ethereum related and raw data related are being displayed. Let’s go through all supported tables to see how data matches with something that you are already familiar with - block explorers. Let’s take transaction with 0x83c0b53f4b9d3c3d454dbffd924b4a390e0b0636f723399839fa92b6efde023e hash :

Let’s try to find the transaction information in ethereum_transaction table. The following query construction setting will have to be set up to get the desired data:

The output can be found at https://www.footprint.network/chart/0x83c0b53f4b9d3c3d454dbffd924b4a390e0b0636f723399839fa92b6efde023e-in-ethereum-transactions-fp-36101

Most of the returned information could be found on the main tab of the transaction overview. Let’s highlight some of the returned fields in the UI:

Let’s switch to another tab in Etherscan - Logs. In complex use-cases your transaction may go through several smart contracts emitting several different events throughout the execution.

To find the corresponding information, you should query the ethereum_logs table. To get the logs of the particular transaction, the query in constructor will have the following look:

https://www.footprint.network/chart/Ethereum-Logs-of-0x83c0b53f4b9d3c3d454dbffd924b4a390e0b0636f723399839fa92b6efde023e-fp-36102

On this Internal Tnxs tab in Etherscan you should be able to see the traces of each particular log:

This is also queryable from Footprint: