Introduction
After you sign and publish an EVM transaction, it usually confirms on its own. When a transaction stays in Published status longer than expected, or the network rejects it, Utila flags it so you can act before other transfers from the same wallet are delayed.
This article explains what the flag means, how to read it, and when to use Accelerate, Revoke, or Republish.
To see flagged transactions, go to Transactions and look for the orange or red indicator next to any Published transaction.
The "needs attention" flag
Utila flags a transaction after it has been published for about five minutes without confirming. There are two indicators:
Indicator | What it means | Typical cause |
Orange warning  | Pending longer than expected, no network error | Network congestion, or the fee is no longer competitive |
Red error 
| The network rejected the transaction | Not enough native token balance for fees, fee below the network minimum, or a publish error |
Why it matters
EVM wallets process outgoing transactions in sequence. If one transaction is waiting, later transactions from the same wallet on the same network wait behind it.
Orange: the transaction is holding its place in line. Other transfers from that wallet queue until you act or it confirms on its own.
Red: the network did not accept this transaction. Later transfers may continue, but this one needs to be resolved or revoked. While it remains in Published there is still a small chance the network picks it up, but do not rely on this.
Incoming deposits are not affected.
Where to find the flag
On the console
Open the Transactions tab and a look for Published transactions with a small flag next to the status.
Click a transaction to open its details in a pane on the right. For those with the flag, you see a warning banner at the top, with details and an action you can take. The color of the banner corresponds to the indication level.
On the mobile app
Open the Transactions tab and a look for Published transactions with a small flag next to the status. Both errors show as red.
Tap a transaction to open its details. For those with the flag, you see a warning banner at the top, with details and an action you can take at the bottom. The color of the banner corresponds to the indication level.
Choose an action
You want to... | Action | What Utila does |
Keep the same transfer and get it confirmed faster | Accelerate | Creates a replacement with the same destination and amount, and a higher network fee |
Drop this transfer and free the wallet | Revoke | Creates a replacement that sends zero to your own address with a higher fee, replacing the original |
Retry the same transaction after fixing the cause | Republish | Rebroadcasts the existing signed transaction. Does not change the fee or amount |
Use the banner's primary button when available. Accelerate and Revoke are approved automatically by policy, so you usually proceed directly to signing.
Accelerate
Use when the transfer is still correct and you are willing to pay a higher network fee.
Typical cases:
The transaction has been pending too long (orange warning). Note that a "mined" state is also considered pending.
The fee is below what the network currently requires.
Another transaction with the same sequence number is offering a higher fee.
You are asked to sign the replacement. There is no guarantee the replacement confirms first. The network includes whichever transaction has the more competitive fee. If the replacement is still pending, you can accelerate again.
Revoke
Use when you no longer want this transfer to go through, such as the destination is wrong, you need to unblock the wallet, or you prefer to send a new transaction instead.
Revoke does not pull funds back from a transfer that has already been confirmed. It only replaces a transaction that is still pending.
Like Accelerate, Revoke creates a new transaction you must sign. The original stays in Published until the revoke confirms, at which point the original is marked Dropped.
Republish
Use after fixing the reason the network rejected the transaction most often, after you provide the wallet with enough native token to cover fees (ETH, POL, BNB, and so on).
Republish sends the same signed transaction again. If the fee was too low, republishing will fail the same way use Accelerate instead. If the wallet is still underfunded, fund it first, then republish.
On a sponsored transfer, the sponsor wallet pays the fee. Fund the sponsor, not the sending wallet.
Revoke vs Cancel
Before the transaction is signed (pending signature), it can still be canceled.
| Cancel | Revoke |
When to use | Transaction not yet signed. | Transaction already signed and published |
What it does | Stops the transaction before it reaches the network | Creates a new on-chain transaction to replace the original |
If the transaction is already Published, use Revoke, not Cancel.
After you accelerate or revoke
A new transaction appears, linked to the original.
Sign it. Until the replacement is signed and published, the original remains the active one in the network.
When the replacement confirms, the old transaction is marked Replaced. Only one transaction can be included.
Later transactions from that wallet proceed in order.
If several replacements are pending, the network usually picks the one with the most competitive fee. You do not need to cancel the others once one confirms.
Troubleshoot using the transaction banner
The warning appeared but the transaction confirmed
This can happen when the network includes the transaction around the same time Utila flags the delay. No action is needed.
I accelerated but the replacement is still pending
Fees may have risen again. Open the latest replacement and accelerate once more, or revoke if you prefer to stop.
I revoked but the original is still Published
The revoke transaction also needs to be signed and included by the network. Check that it is in Published and that its fee is competitive. You can accelerate the revoke if it is waiting.
Later transactions from this wallet are not moving
The mobile app indicates that a transaction is queued and links directly to the transaction blocking it. Follow that link and accelerate or revoke the blocking transaction first.
Accelerate or Revoke is missing
The transaction may already be mined, replaced, or on a network that does not support replacement. Refresh the page. If it is still in Published and the actions are missing, contact Utila support with the transaction ID.
I don't have the signing device with me
The replacement requires a signature from an authorized signer (mobile app or co-signer). Ask another vault signer, or complete it when the device is available. Leaving the replacement unsigned keeps later transfers queued.
Related articles