Turning a block scan into a database query
The gap between 'data exists on-chain' and 'data is queryable' is closed by indexing infrastructure. An indexer is a piece of software that watches a blockchain as new blocks are produced, processes each one as it arrives, and writes the relevant results into a structured database, one built with the same kind of tables, fields, and query capabilities as any other application database. Instead of an analyst scanning raw blocks every time a question comes up, the indexer has already done that scanning once, continuously, and organized the results so that answering a question becomes a database lookup rather than a fresh block-by-block search.
This reframes the earlier example completely. 'How many unique addresses interacted with this contract last month' stops being a request to replay millions of transactions and becomes a query against a table that already tracks, per contract, which addresses have interacted with it and when. The heavy lifting happened once, incrementally, as each block arrived, rather than being repeated from scratch for every question asked. That shift, from 'scan everything on demand' to 'query a pre-built structure,' is the entire value indexing provides.