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.

EIP-7702 Support (Live as of May 7, 2025)

EIP-7702 (enabled with Ethereum’s Pectra hardfork) introduces a new transaction type (type = 4) that lets EOAs delegate execution to a contract. The authorization_list includes the delegated address, chain ID, nonce, and signature data (r, s, yParity). Allium has done the work to embed authority directly in the authorization_list, enabling identification of the delegated source — built using logic from viem.

authorization_list allows you to:

  • Detect if an EOA has become a smart wallet
  • Identify the contract it delegated to
  • Determine which chain the delegation occurred on

✅ Live on: Ethereum, BSC

⏳ Enabled and awaiting data: Base, Worldchain, Optimism, Polygon, Arbitrum, Unichain

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 NameDescription
block_numberThe length of the chain, in blocks.
block_timestampThe time when the block that contains this transaction was included on the blockchain.
block_hashUnique identifier of the block that includes this transaction.
hashUnique identifier of a transaction.
nonceThe transaction nonce, unique to the wallet
transaction_indexThe position of this transaction in the block that it belongs to. The first transaction has index 0.
from_addressThe address of the sending party of this transaction.
to_addressThe address of the receiving party of this transaction (could be a contract address).
valueThe amount of ether sent in this transaction, in wei.
gasThe maximum amount of gas allocated for this transaction in wei.
gas_priceCost per unit of gas specified by the transaction in wei. The higher the gas price, the higher chance of getting included in a block.
inputThe data sent along with the transaction.
max_fee_per_gasThe maximum fee per gas that the transaction sender is willing to pay for this transaction (introduced in EIP1559)
max_priority_fee_per_gasThe 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)
l1_base_feeL1 base fee at the time the transaction was submitted
receipt_gas_usedThe total amount of gas consumed by a transaction as recorded in its receipt
receipt_cumulative_gas_usedThe total amount of gas used when this transaction was executed in the block.
receipt_effective_gas_priceThe sum of the base fee and tip paid per unit of gas.
receipt_contract_addressThe contract address created, if the transaction was a contract creation, otherwise null.
receipt_rootTransaction stateroot (pre Byzantium).
receipt_statusSuccess status of the transaction. Either 1 (success) or 0 (failure).
receipt_l1_block_numberThe L1 block number where this L2 transaction was finalized
receipt_l1_feeThe Layer 1 fee paid for the transaction (applicable for Layer 2 transactions).
receipt_l1_fee_scalarMultiplier used to adjust L1 data fees for L2s (applicable for Layer 2 transactions).
receipt_l1_base_fee_scalarThe base fee scalar component applied to L1 base fee to calculate L1 data costs for rollups (applicable for Layer 2 transactions).
receipt_l1_gas_priceThe gas price used to compute L1 calldata fee (applicable for Layer 2 transactions).
receipt_l1_gas_usedThe amount of gas used on the L1 chain for posting transaction data (applicable for Layer 2 transactions).
receipt_gas_used_for_l1The amount of gas used for L1 data submission for the L2 transaction
receipt_l1_blob_base_feeBase fee per blob (in wei) on L1 (post-EIP-4844) (applicable for Layer 2 transactions).
receipt_l1_blob_base_fee_scalarScalar applied to blob base fee to adjust L1 blob costs on L2 (applicable for Layer 2 transactions).
receipt_blob_gas_usedTotal blob gas used for the transactions
receipt_deposit_nonceNonce used to track L1→L2 deposit transactions, for tracking cross-chain deposits and preventing replay attacks.
receipt_deposit_receipt_versionVersion identifier for the L1 deposit receipt format.
log_countNumber of event logs emitted in the transaction.
transaction_typeThe integer of the transaction type, 0x0 for legacy transactions, 0x1 for access list types, 0x2 for dynamic fees.
authorization_listAn array of objects present in 7702 transactions, each containing the delegated address, chain ID, nonce, signature data (r, s, yParity), and the recovered authority.
access_listA list of addresses and storage keys that the transaction plans to access, introduced in EIP-2930 to help optimize gas costs.
y_parityThe parity (0 or 1) of the y-coordinate of the curve point for the signature’s recovery identifier.
beneficiaryAddress receiving block rewards or fees
deposit_valueAmount bridged from L1 in a deposit transaction
max_submission_feeMaximum fee paid for submitted a retryable ticket (for Arbitrum Orbit chains)
retry_toTarget address of the retryable transaction on rollups (for Arbitrum Orbit chains)
retry_valueETH value sent with the retryable transaction (for Arbitrum Orbit chains)
retry_dataCalldata payload for the retryable execution (for Arbitrum Orbit chains)
refund_toAddress receiving any unused submission fee refunds (for Arbitrum Orbit chains)
request_idUnique identifier for L1-to-L2 messages or retryable tickets (for Arbitrum Orbit chains)
max_refundThe maximum amount that can be refunded to the user if the retryable ticket is canceled or not executed (for Arbitrum Orbit chains)
ticket_idThe unique identifier (message hash) for a retryable ticket used in Arbitrum’s L1 → L2 messaging system (for Arbitrum Orbit chains)
submission_fee_refundThe portion of the submission fee returned to the user (for Arbitrum Orbit chains)
indexPosition index of the transaction within a sequence, returned from the RPC response.
l1_block_numberBlock number on L1 where this L2 transaction originated
l1_timestampTimestamp of the L1 block where this L2 transaction originated
l1_tx_originOriginal sender address on L1 that initiated this L2 transaction
queue_indexPosition in the L2 transaction queue
queue_originOrigin of the transaction in the queue
seq_rR component of the sequencer’s signature
seq_sS component of the sequencer’s signature
seq_vV component of the sequencer’s signature
raw_transactionComplete raw transaction data in hexadecimal format
deposit_receipt_versionVersion identifier for the deposit receipt format used in L1->L2 deposits
deposit_receipt_nonceUnique nonce used to track and verify L1->L2 deposit transactions
_extra_fieldsAny additional fields that aren’t explicitly defined
_created_atTimestamp of the entry creation.
_updated_atTimestamp of the entry update.