Transactions

Transactions, which change the state of the EVM, need to be broadcast to the whole network. Any node can broadcast a request for a transaction to be executed on the EVM; after this happens, a validator will execute the transaction and propagate the resulting state change to the rest of the network.

Table Columns

Column Name	Description
hash	Unique identifier of a transaction.
nonce	The transaction nonce, unique to the wallet
transaction_index	The position of this transaction in the block that it belongs to. The first transaction has index 0.
from_address	The address of the sending party of this transaction.
to_address	The address of the receiving party of this transaction (could be a contract address).
value	The amount of ether sent in this transaction, in wei.
gas	The maximum amount of gas allocated for this transaction in wei.
gas_price	Cost per unit of gas specified by the transaction in wei. The higher the gas price, the higher chance of getting included in a block.
input	The data send along with the transaction.
receipt_cumulative_gas_used	The total amount of gas used when this transaction was executed in the block.
receipt_gas_used	Gas consumed by the transaction in wei.
receipt_contract_address	The contract address created, if the transaction was a contract creation, otherwise null.
receipt_root	Transaction stateroot (pre Byzantium)
receipt_status	Success status of the transaction. Either 1 (success) or 0 (failure).
block_timestamp	The time when the block that contains this transaction was included on the blockchain.
block_number	The length of the chain, in blocks.
block_hash	Unique identifier of the block that includes this transaction.
receipt_effective_gas_price	The sum of the base fee and tip paid per unit of gas.
max_fee_per_gas	The maximum fee per gas that the transaction sender is willing to pay for this transaction (introduced in EIP1559)
max_priority_fee_per_gas	The maximum fee per gas the transaction sender is willing to give to validators (Proof of Stake) or miners (Proof of Work) to incentivize them to include their transaction (introduced in EIP1559)
transaction_type	The integer of the transaction type, 0x0 for legacy transactions, 0x1 for access list types, 0x2 for dynamic fees.

Other Advanced Fields

• input

  • The binary data that forms the input to the transaction. For example, contract function call information is recorded here.

• transaction_type

• receipt_root