Skip to main content
In progress. This table is not served yet. The page documents it as it lands.
facts.chain_transactions contains one row per transaction on a covered network, with the fee that transaction paid. Every covered network lands in this same table, so one query spans them all. project_id is worked out from dimensions.chains when the table is read, so a change of operator flows into every row.

Columns

ColumnTypeDescription
block_timestampTIMESTAMPThe time of the block containing the transaction. Partition column of the underlying sources.
transaction_hashSTRINGHash of the transaction.
chain_idSTRINGChain the transaction executed on.
project_idSTRINGProject running the chain, taken from dimensions.chains.
from_addressSTRINGAddress that sent the transaction.
token_addressSTRINGAddress of the chain’s own gas token, the one the fee is charged in.
fee_amountFLOAT64Fee the transaction paid, in units of that gas token.

Sample queries

The table is partitioned on block_timestamp. A query bounded on that column reads only the days it needs. Bound it in every query.
Rank addresses by fees paid on one chain over one week. We publish no per-address totals, so a figure per address is worked out straight from the transactions.

Notes

fee_amount is in units of the chain’s gas token rather than in USD, and token_address names that token. The daily fee total per chain in USD is already worked out on Chains β–Έ Metrics, where reading it costs a single day of data.