Recently someone asked me: why do on-chain data sometimes "pause" briefly, even though the blocks have already been produced. To put it simply, many times it's not the chain slow, but the layer you're viewing is slow: the frontend first makes an RPC call to fetch events, and when RPC rate limits, it has to queue; the indexer/Subgraph also needs to fetch logs, replay them, write to the database, and then serve your queries. If any step stutters, you'll see prices/positions appear to freeze for a moment. Layer2 now constantly debates TPS, fees, subsidies, but I think the stability of these "data pipelines" actually impacts the user experience the most. No matter how generous the subsidies are, if users see loading spinners, they'll complain. Staring at these things for a long time makes my eyes a bit sore, and my neck stiff... I now prefer to refresh a little less often, keeping key data locally for verification, to avoid being "paused" and influenced by the rhythm.