midnight-indexer:indexer-data-model

You query Midnight blockchain data by mapping on-chain records into a relational database and accessing them through a GraphQL API. This enables fast, flexible queries across blocks, transactions, contract actions, and ledger events for analytics dashboards.

The Midnight indexer data model covers blocks, transactions, contract actions, contract balances, unshielded UTXOs, ledger events, DUST generation, system parameters, and SPO data. These entities are structured in core tables with clear relationships for cross-entity querying.

The indexer lifecycle processes data from block finalization through to event processing, systematically mapping finalized on-chain data into relational database tables. This structured pipeline ensures reliable data access for downstream applications.

Yes, the indexer schema defines contract tables, token and UTXO tables, wallets, and governance structures with clear entity links. You can trace contract lifecycles and generate governance reporting by querying these related database tables.

The best way to start is running a sample query against the indexer's GraphQL API to fetch blocks and related entities for a specific block height. This allows you to verify data coverage and relationships across the relational schema.

Yes, the Midnight indexer requires a relational database to store on-chain data. It maps blocks, transactions, balances, and ledger events into core tables to enable fast queries and reliable data access for downstream apps.