Logs

The Ethereum Logs Table is a Raw Dataset which is used to record and store events emitted by smart contracts during transactions. These logs are essential for developers and users to track specific events like token transfers, approvals, or other contract-specific activities. Before we delve into how we have built our raw ethereum_logs dataset, it is important to understand what are data and topics to better decipher the tables and build better analytic solutions to understand the blockchain events. Our Raw ethereum_logs dataset consist of the following columns with the corresponding data types:

Data Types

Columns
Data Types

log_index

bigint

transaction_hash

string

transaction_index

bigint

address

string

data

string

topics

array<string>

block_timestamp

timestamp

block_number

bigint

block_hash

string

Key Descriptions of Columns in Ethereum Logs Table

  1. log_index: A sequential identifier used to distinguish logs if multiple logs are included in a single transaction.

  2. transaction_hash: A unique identifier for each transaction. It is used to track and reference specific transactions within the blockchain.

  3. transaction_index: The relative position of a specific transaction in a block.

  4. address: Address of the contract that generated the particular log.

  5. data: Arbitrary data that the contract decided to log. This can include encoded important values such as amounts transacted, addresses involved, etc. This is in hexadecimal format. You can read more about data in our blogs.

  6. topics: Topics represent indexed arguments in the logs that are generated by smart contracts during transactions. Topics are a fundamental part of how data is indexed and queried in Ethereum logs, enabling efficient searching and filtering of log entries.

  7. block_timestamp: The exact date and time when the block was mined. This helps in tracking the block creation rate and understanding network activity over time.

  8. block_number: A unique identifier for each block in the blockchain. It indicates the block’s position in the entire chain, starting from the genesis block.

  9. block_hash: A unique hash of the block. It serves as the block’s fingerprint and is used to securely link blocks in cryptographic chains.

Last updated