Transactions
Transactions are cryptographically signed instructions from accounts.
An account will initiate a transaction to update the state of the blockchain network. Transactions always originate from an externally owned account (a smart contract can not initiate a transaction). 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.
Learn more in the official Ethereum documentation here.
Transaction Fees
For detailed metrics on transaction fees in native tokens and USD, including average transfer costs, see Metrics.
Transaction fees vary across different blockchains. Layer 1 chains typically have a single fee component, while Layer 2 chains include both L1 and L2 fees. Each chain may handle system transactions and fee calculations differently.
Table Columns
Several columns may only be applicable for specific EVM-compatible blockchains. The list of columns present in the table is not exhaustive.
Unique Key: hash
| Column Name | Description |
|---|---|
| block_number | The length of the chain, in blocks. |
| block_timestamp | The time when the block that contains this transaction was included on the blockchain. |
| block_hash | Unique identifier of the block that includes this transaction. |
| 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 sent along with the transaction. |
| 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) |
| receipt_cumulative_gas_used | The total amount of gas used when this transaction was executed in the block. |
| receipt_effective_gas_price | The sum of the base fee and tip paid per unit of gas. |
| receipt_l1_fee | The Layer 1 fee paid for the transaction (applicable for Layer 2 transactions). |
| 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). |
| log_count | Number of event logs emitted in the transaction. |
| transaction_type | The integer of the transaction type, 0x0 for legacy transactions, 0x1 for access list types, 0x2 for dynamic fees. |
| _created_at | Timestamp of the entry creation. |
| _updated_at | Timestamp of the entry update. |