How to Resolve Pending Transactions on Stacks?

Pending transactions can be a frustrating experience. Here’s a guide to help you understand why they occur and how to address them.

Why Are My Transactions Stuck?

Pending transactions can occur for various reasons, including:

  • High network congestion: When the network is congested, it prioritizes transactions with higher fees, causing delays for those with lower fees.
  • Incorrect nonce: Each transaction is assigned a unique nonce by the wallet, which must follow a specific sequence. If this sequence is disrupted, transactions can get stuck.

Can I Cancel My Pending Transactions?

Due to the decentralized nature of blockchain technology, once a transaction is initiated and broadcast to the network, it generally cannot be canceled. The transaction's inclusion and confirmation are controlled by the network, not by the Xverse wallet.

While you cannot cancel a transaction, you can replace it with another. For more details, check out our guide: How to Replace an Existing Transaction?.

Important Note:

  • Once a transaction is confirmed on any network, it cannot be reversed or canceled.
  • Transactions pending for 256 blocks (approximately 2-3 days) after being submitted will automatically be removed from the mempool.

Resolve a Pending Transaction due to Low Fee

To speed up a pending transaction in Xverse, go to your Stacks Dashboard and find the pending transaction. Select the “Speed Up” option, which will allow you to adjust the transaction fee. By increasing the fee rate, you can prioritize the transaction and make it process faster on the network. After setting the new fee, click "Submit" to finalize the process.

Xverse Support Visuals.jpg

 

Resolve a Pending Transaction due to Wrong Nonce

If you discover your transaction is stuck due to an incorrect nonce, follow these steps:

Step 1: Identify the Pending Transactions

Visit https://explorer.hiro.so/ search for your address, review your pending transactions and find the “last executed nonce”.

Xverse Support Visuals (1).png

Step 2: Determine the correct nonce

If your last transaction used a nonce value of x, the next one should use nonce x+1. Thus, the correct nonce for the next transaction in this example is 22.

Step 3: Replace the pending transaction with the correct nonce value

You can create a new transaction, on the Review transaction screen, edit the nonce to correct value, adjust the Network Fee to high priority for faster processing.

Xverse Support Visuals.jpg