Your transaction is stuck and you cannot tell whether it is you or the network. This reads block production directly from sixteen chains and tells you which are running normally, which are late, and which have stopped producing blocks entirely.
Is it me or is the chain down? When a transaction sits unconfirmed the first question is whether the network is still producing blocks. This reads block production directly from each chain. If the newest block is minutes old, the chain has stopped and nothing you do to your transaction will help until it restarts.
Every chain has a cadence, the interval it is designed to produce blocks at. Ethereum aims for twelve seconds, most rollups for one or two. A chain is judged here against its own cadence rather than a single threshold, because five seconds is normal on Ethereum and a long time on Arbitrum.
Round trip time is how long the public node took to answer. A slow node is not a slow chain, and the two are worth keeping separate: if latency is high but blocks are current, the chain is fine and the node is busy.
Usually a consensus bug or a client upgrade going wrong, occasionally an overload. It happens more often than the industry likes to discuss, and it is one of the practical differences between chains that rarely appears in a comparison table. A chain that has halted repeatedly is telling you something about its engineering maturity, and that is a legitimate input into where you hold value.
Check the chain above first. If it is producing blocks normally then the chain is fine and your transaction is either underpriced, waiting behind others, or dependent on something that has not happened yet. If the newest block is minutes old on a chain that normally produces one every two seconds, the network has stopped and nothing about your transaction is the problem.
No. A pending transaction on a halted chain is queued rather than lost, and it will be included when production resumes. Resubmitting often means paying twice, because both copies can confirm. Raising the fee also achieves nothing: fee priority orders transactions against each other, and nothing is being ordered while the chain is stopped.
How many seconds ago the most recent block was produced. Judged against that chain\u2019s own cadence, since twelve seconds is normal for Ethereum and would be a long delay on a rollup that produces blocks every two seconds. Five seconds old on Ethereum is healthy. Five seconds old on Arbitrum, which aims for a fraction of a second, is worth watching.
Not necessarily, and the distinction matters. That means the public node used here did not respond, which is often the node being busy rather than the chain having stopped. Check a second source or the chain\u2019s own status page before concluding anything.
Yes, more often than the industry likes to discuss. Usually a consensus bug or a client upgrade going wrong, occasionally overload. Several well known chains have halted for hours. It is one of the practical differences between networks that rarely appears in a comparison table, and a chain that has halted repeatedly is telling you something real about its engineering maturity.
We seal the list every week and keep re-checking every token on it, so you can see what actually happened to them rather than only what is trading today.
