You send a token, the transaction confirms in a couple of seconds, and then you open your wallet's activity tab and the transfer is not there yet. A minute later it appears. Or you check your balance in one app, then open a different app and see a slightly different number for the same wallet. Neither of these is a bug, and neither means something went wrong with your transaction. They are both side effects of a layer of infrastructure that sits between the blockchain itself and the app you are looking at, called an indexer.
The chain is not built for quick lookups
A blockchain like Base is very good at one thing: agreeing on what happened, in what order, permanently. Every node keeps a copy of the full history and can tell you the current state of any account or contract. What it is not good at is answering broad questions quickly, things like "show me every transfer this wallet has ever received" or "list all the swaps that happened on this pool in the last month."
Answering a question like that by asking the network directly would mean scanning block after block, transaction by transaction, checking each one for a match. A node can technically do this, but it is slow, and it would be far too slow to run every time an app loads a page. Blockchains are optimized for consensus and security, not for search.
What an indexer actually does
An indexer solves this by doing the scanning work once, continuously, in the background, rather than every time someone asks a question. It watches new blocks as they arrive, reads the transactions and event logs inside them, and organizes that raw data into a structured, searchable form, usually a database designed to answer exactly the kind of questions an app needs to ask.
Once that structured copy exists, an app can query it directly and get an answer in milliseconds instead of scanning the chain from scratch. This is the layer that powers almost every wallet history view, portfolio dashboard, and block explorer search box you have ever used. Base's own developer documentation lists more than a dozen indexing services that projects can build on, some using GraphQL query languages, some built around a format called a subgraph, others focused on raw speed or enriched, human readable data. The details differ, but the underlying job is the same: turn the chain's raw ledger into something an app can search quickly.
Why this creates small, harmless gaps
Because an indexer processes blocks after they happen rather than before, there is always a small delay between a transaction confirming on chain and that same transaction showing up in an indexed view. Most of the time this gap is a few seconds. Occasionally, if an indexer is catching up after a hiccup or a network is unusually busy, it stretches to a minute or two.
This also explains why two different apps can show two different balances or activity lists for the same address at the same moment. Each app may rely on a different indexing service, refresh on a different schedule, or choose to display slightly different information, pending transactions included or excluded, small dust amounts filtered out or shown, and so on. None of these differences change what actually happened on chain. The chain itself has exactly one answer for what your balance is at any given block. The apps are just different windows looking at that answer through slightly different, slightly delayed lenses.
Where to look when you want the source of truth
If a balance or transaction ever looks wrong or missing and you want to settle it, skip the guessing and go to a block explorer like Basescan. An explorer reads much closer to the chain itself and lets you look up a wallet address or a transaction hash directly. If a transfer shows there with the details you expect, it happened, regardless of what any single app's dashboard currently displays. If you want to understand what a transaction record on an explorer is actually telling you, our guide on using a block explorer walks through the layout, and our piece on transaction receipts and event logs goes a level deeper into how that raw data is structured in the first place.
It is also worth remembering that an indexing lag is purely a display issue. It has no effect on your funds, your approvals, or the actual state of your wallet on chain. Nothing needs refreshing, resubmitting, or fixing. The transaction already settled the moment it confirmed; the only thing catching up is the view.
The takeaway
A blockchain records what happened. An indexer decides how quickly and in what shape you get to see it. When an app's history feels a step behind, or two apps briefly disagree, that is this layer doing its job, not a sign that anything is broken. For anything that actually matters, a payment landing, a swap completing, checking the chain directly through an explorer will always give you the real answer while the rest of the apps catch up.