Recently, many people have been saying that on-chain data "lags," but it's not necessarily the chain being slow; mostly, it's your indexer/subgraph/RPC choking. The subgraph needs to scan blocks and parse events; when encountering reorganizations or node replays, it will temporarily revert and rebuild. RPC rate limiting is also very real; opening too many concurrent requests at once causes responses to start drifting. The most annoying part is that the frontend caches old results, making you think you're seeing things. To put it simply, data isn't "real-time," it's "as close to real-time as possible." What I don't regret is... that time I got stuck on nonce issues, I stubbornly fixed the script to automatically slow down and retry + switch to backup RPCs, otherwise I’d probably still be cursing the network now. By the way, regarding the recent NFT royalty disputes, many of the "trade/order" numbers are also affected by these delays. Everyone, don’t rush to blame each other; first check if the data source is acting up again... Anyway, my first reaction when I see lag is: check rate limiting, then check the index height.