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
| Column | Type | Description |
|---|---|---|
block_timestamp | TIMESTAMP | The time of the block containing the transaction. Partition column of the underlying sources. |
transaction_hash | STRING | Hash of the transaction. |
chain_id | STRING | Chain the transaction executed on. |
project_id | STRING | Project running the chain, taken from dimensions.chains. |
from_address | STRING | Address that sent the transaction. |
token_address | STRING | Address of the chainβs own gas token, the one the fee is charged in. |
fee_amount | FLOAT64 | Fee the transaction paid, in units of that gas token. |
Sample queries
- Top fee payers
- One address, daily
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.