Sometimes it's not just that you clicked confirm and "sent it out," the mempool is actually like waiting in line, and when congestion hits, people start pushing and shoving. Your transaction might be sitting in your local wallet first, then broadcasted and picked over by nodes, with low gas fees causing it to be left hanging; what's more awkward is that you think it failed and resend, only to find two transactions stuck in the queue, or the previous one not confirmed on-chain and the dependent transaction just stalls in place. Some people take advantage of the chaos to cut in line or sneak a move (in plain terms, matching and front-running you without you seeing), and by the time you realize, the best moment to act has already passed.

Recently, everyone’s talking about modularization and the Data Availability layer, and developers are excited as if it's the New Year, while users are confused: I just want to transfer some funds, why do I also need to understand "where the data is stored"? Anyway, when I encounter congestion now, I don’t push back hard; I first review the old authorizations in my wallet and revoke what I can, and note down the nonce of the stuck transaction so I don’t get myself tangled up.