Recently someone asked me: why does on-chain data always "pause" for a moment, even though blocks are already produced. To put it simply, many front-end applications do not read directly from the chain, but go through indexers/Subgraphs, which are "organizing first and then providing" methods; if the indexer is lagging behind, reverts during reorganization, or the queue is piled up, you'll see balances/positions freeze then jump again. Plus, RPC rate limiting makes it more realistic: free nodes get a 429 when busy, wallets/browsers can only retry, giving the feeling of lag.

By the way, now there's a lot of noise about staking and shared security "yield stacking," but I care more about whether the underlying data sources are nested in the same layer: one RPC, one subgraph, on-chain is fine, but off-chain services are struggling first. Anyway, when I encounter anomalies, I first compare the original events and different RPCs to see if it's a "display issue," rather than immediately suspecting the contract has been hacked.