Actually, everyone understands that when a chain gets congested, your transaction is just like an order in a food delivery app—queued in the mempool first. If you don’t shout loud enough (pay enough fee), you’ll keep getting pushed back... Last night, I didn’t believe in that, thinking I just wanted to batch transfer a few small amounts. But I ended up stuck for a long time, watching blocks pass one after another. My transaction was blocked by an air wall, and I was so anxious I kept refreshing.

What’s more frustrating is that some on-chain data tools/tags still give you the illusion of “already confirmed/no problem,” when in fact, the mempool is still fighting, or someone else has cut in line, and you don’t even know. Now I basically have two tricks: either go straight to L2/Account Abstraction for peace of mind, or admit defeat and wait until the congestion eases before sending, so I don’t have to keep fiddling with gas and sneezing from frustration... Anyway, I’m not in a rush to be the first to launch.