Cosmos account sequence mismatch: why a transaction is rejected
The transaction was signed with an account sequence that does not match the chain's expected sequence. Another transaction or stale wallet data can cause this.
The interactive tool loads with JavaScript. Network-dependent values are retrieved when the tool opens; no live rate or account balance is assumed here.
Step 1
Check whether your earlier transaction was included. Avoid repeatedly broadcasting new transfers while the result is uncertain.
Step 2
Refresh the wallet's account data and let any earlier transaction settle before preparing a new transaction.
Step 3
Rebuild and sign the transaction with fresh account information. Developers should coordinate sequence numbers when sending from the same account concurrently.
Understanding the result
A sequence error alone does not tell you whether a different transaction succeeded. Check the hash and account activity; do not assume a refund is pending.