Today I was taught a lesson by the mempool again... When there's congestion, the transaction you send out is basically "抢座位" (抢座位) in line, first look at whether the fee you provided is enough, if not, it just stays stuck, or even gets cut in line by someone behind (in other words, those who pay more get packaged first). What's more annoying is that you think "submitted = secure," but in reality, it might spread slowly between nodes, or be replaced by someone else's transaction with a higher fee at the same nonce, and your wallet interface still looks quite calm.

Some people use labels from on-chain data tools to judge "who's causing trouble," but I have some reservations now. The lagging/being misled by labels is really not a conspiracy theory; during congestion, messages spread slowly, and on-chain looks even more like "armchair quarterback." I plan to later grab a few transaction hashes during peak times to compare the time differences seen by different nodes, just like that for now.