Skip to main content
stacks holds the standardized Stacks tables. Stacks sits on top of Bitcoin and runs contracts of its own, written in a language called Clarity, so its tables differ from the rest of the Bitcoin family: blocks and transactions carry extra columns for that, and a third table, events, records asset movements, locked STX (the chain’s own token), and the notes its contracts write.

Tables

TableSinceDescription
blocks2024-04One row per block, with burn-block anchoring and execution cost totals.
transactions2024-04One row per transaction, with the columns its Clarity type populates.
events2021-01One row per event: asset transfers, STX locks and contract logs.

Sample queries

Count events by type on one day.

Notes

blocks and transactions start on 2024-04-16, so events is the only table with history before 2024. Transactions are keyed on transaction_id, and events on transaction_id and event_index. Stacks transactions come in several kinds, and transaction_type says which. Which columns are filled in follows from that: token_transfer_* for a transfer, contract_call_* for a call into a contract, smart_contract_* for publishing one. The rest are empty. Because Stacks runs contracts, its tokens reach the catalog’s token list where the rest of the Bitcoin family’s do not, and some carry a daily USD price. No app, pool or tokenized asset table covers Stacks. Tokens covers the token list and the daily price table in depth. Chains covers the list of chains we track.