Table description
The traces table, also known as the “snapshot” table, stores relevant on-chain state data that are otherwise difficult to acquire from base Substrate tables such as extrinsics and events. The traces tables are populated with special scripts modeling key storage elements at the end of the hour or day. Having these snapshots enables Dune analysts to build useful dashboards on Dune such as:Table Schema
| Column | Type | Description |
|---|---|---|
year | INTEGER | Calendar year of the snapshot (partition column) |
month | INTEGER | Calendar month of the snapshot (partition column) |
section | VARCHAR | The pallet (module) of the storage item being traced |
storage | VARCHAR | The specific storage item name being traced |
ts | TIMESTAMP | Timestamp of the state snapshot |
block_number | BIGINT | The block number at which the snapshot was taken |
block_hash | VARBINARY | Hash of the block at which the snapshot was taken |
chain_name | VARCHAR | Name of the Substrate chain (e.g. polkadot, kusama, hydradx) |
address_ss58 | VARCHAR | SS58-encoded address associated with this trace entry |
address_pubkey | VARBINARY | Public key associated with this trace entry |
track | VARCHAR | Category or governance track for grouping trace data |
track_val | VARCHAR | Value associated with the track |
kv | VARCHAR | JSON-encoded key-value data from the storage item |
pv | VARCHAR | Protocol version or parameter value |
source | VARCHAR | Source or origin of the trace data |
updated_at | TIMESTAMP | When this record was last updated in the database |
ingested_at | TIMESTAMP | When this record was first ingested into the database |