Regarding your comment “Why does on-chain data always lag a bit”... many times it's not the chain lagging, but the layer you're viewing is struggling. Frontends generally don't directly query nodes; they rely on indexers/Subgraphs to organize on-chain logs into queryable tables first. They need to track new blocks, perform rollbacks and re-computations, and queue database writes. When there's congestion or node hiccups, they fall behind, and you feel like “it just didn't update earlier.” Plus, RPC rate limiting is more realistic: when traffic is high and requests come in rapidly, you get 429 errors or queuing, and wallets and DApps just spin in circles, actually being throttled at the faucet.

Recently, with the news of increased taxes and tighter compliance, everyone's first reaction is “quickly deposit, withdraw, or switch chains,” causing request volumes to spike instantly, making lag even more noticeable. Anyway, when I see data delays now, I first check whether the subgraph is still catching up with blocks or if RPC is rate-limited, rather than immediately thinking I made a mistake.