Staring at the wallet spinning for those few seconds is really nerve-wracking... During congestion, a transaction entering the mempool is like entering a waiting hall: you take a number and queue up, miners/validators pick the "more expensive" tickets first, and the rest continue to sit on the cold bench. What's more embarrassing is that you think you've sent it out, but you've only broadcasted successfully; the chain hasn't stamped it yet. In the middle, it might be replaced by another transaction with a higher fee, or you might have to increase your bid to "rush" the transaction. So sometimes it's not that the contract is broken, but that the queue is too long + your bid isn't high enough. Recently, social mining has been quite similar... Attention is also on queuing, whoever "raises the bid" more will be seen first. Anyway, I first set clear limits on the fee and timeout strategies, so I don't emotionally chase the confirmation button.