Today, while running tasks, I again ran into those moments of “data getting stuck.” Even though the block has already been produced on-chain, the page is still just spinning. To put it plainly, a lot of the time it’s not that your network is bad—it’s that the indexer/Subgraph hasn’t scanned the new data yet, or the RPC is being rate-limited: when too many people use the free nodes, you end up queued; after that, your wallet/frontend retries a few times, and it looks like things are lagging on and off. I’ve basically gotten used to it now—I handle important operations by checking the transaction hash on a block explorer first, rather than staring at the panel and scaring myself. That said, recently I’ve also been hearing about increased taxes and tighter compliance in some areas. Once people’s expectations for deposits and withdrawals get tighter, on-chain lookups and withdrawal actions become even more frequent, and the feeling of lag is even more obvious… In any case, what I can do is work out the route clearly, account for Gas and bridge costs, and just wait two minutes when it gets stuck—don’t get worked up.