A transaction appearing in an index is not necessarily a permanent record. In an article published on November 12, 2026, at 18:40 (UTC+8), LearnBlockchain explains how a chain reorganization can invalidate transactions that a subgraph, indexer or data API has already processed.
Consider the article’s example of Alice transferring funds to Bob. If a reorganization removes that transfer from the canonical chain, deleting its transaction record alone is insufficient. An indexer must also reverse changes to related entities, balances, total value locked (TVL) and aggregate statistics, then process the canonical chain. Otherwise, an API may return figures that no longer match the chain it is meant to represent.
The article distinguishes data freshness from finality. Data drawn from the latest chain state may be more current, while using safe or finalized states involves a different trade-off between timeliness and confidence that the data will persist. Consistency also extends beyond the indexer: API caches, downstream business state and notifications that an event has been withdrawn can retain or propagate invalidated information.
For readers evaluating an indexing service, the article points to canonical-chain detection, state rollback and reprocessing, consistent snapshots, recovery from deep reorganizations and observability. These capabilities matter because a query result reflects an indexer’s view at a particular point—not an assurance that every underlying transaction will remain on the canonical chain.