Here is how Scout organizes the Ethereum transaction data. To make it easy to remember, we are comparing what a transaction looks like on Scout with that on Etherscan.
Now, let's dive into each data field of the Transactions data source: (Fields marked with🌶are the most important ones.)
transactionHash: The unique identification of a transaction.
from: The party that initiated this transaction. It is always an Externally Owned Account, commonly known as a wallet address.
contractAddress: Most transactions nowadays have a smart contract involved. This is the address of that smart contract. If the value is null, it means this transaction is a contract creation transaction.
logs🌶: This is the most important field to track protocol metrics. A single transaction can contain multiple logs. Software developers typically put logs inside a smart contract. When certain actions of the smart contract are executed, logs are the footprints that a smart contract leaves on the Ethereum blockchain.
blockNumber and blockTimestamp: The block number and the time when this transaction happened. BlockTimestamp is in UTC format.
function: The smart contract function that was executed in this transaction. This is another useful field you would use to track protocol/dApp metrics. Only one function can be executed in a transaction. The function is an object type and it also contains a few children fields:
name: The name of a function. Different smart contracts can have the exact same function names. For example, every ERC20 token contract has a function called "transfer". To identity a specific function, it's best to use both the name of this function and the contractAddress of a transaction.
methodId: This is a value encoded based on the name and parameters of a function. Its uniqueness is not completely guaranteed. Most time, you don't need to pay attention to this value. More technical details can be found here.
params: These are the parameters of a function. If you are not a coder and don't understand what "the parameters of a function" means, it's totally fine. Just remember that from time to time, important metrics data will be stored in this field as well.
success: It has two values. If the transaction was successful, the value is true; If not, the value is false.
gasPrice: The price of the gas when the transaction was executed. The unit is in Wei.