Queue
Track and manage multisig transactions waiting for signatures or execution
The Queue is a list of multisig operations that were created for the account but are not yet fully executed. The number of new operations requiring your attention is displayed on the counter near the Queue menu item.
Each operation uses a nonce and requires a certain number of signatures from account members. Transactions must be processed in order: an operation with a smaller nonce needs to be executed before any operation with a larger nonce.
Queue list
The information on this page is divided into tabs.
On this tab, you can view a list of operations that are still waiting for signatures or execution.
The first block on the tab highlights the transaction that needs to be executed first. This block corresponds to the operation with the smallest Nonce in the queue.
The following information is provided about each pending operation:
Nonce
The sequential number used by the smart contract to keep transactions in the correct order.
The queue is sorted from the smallest nonce to the largest.
Created at
The time when the operation was added to the queue.
The value is shown as relative time (for example, 5 minutes ago) and can be viewed as a date and time in the details.
Operation
The type of the pending operation.
Possible values:
Payout
Multisig config change
Reject
Amount
For operations that change balances: the amount of the transaction.
Amounts that reduce the balance are shown with a minus sign and include the currency, for example -1,056.06 ETH.
For configuration operations, the value displays —.
Signatures
The number of collected signatures versus the required number, in the X/Y format (for example, 2/5 or 5/5).
Action
The set of actions available for the current user and operation state.
Possible values:
Sign: Available if the current user has not yet signed the operation and is allowed to sign it.
Execute: Available when all required signatures are collected and the operation has the smallest nonce in the queue.
When an action is not available, the corresponding button is disabled or hidden.
Operation details
Click the chevron icon to expand the operation details:
Created at
The date and time when an operation was created.
Created by
The account name and address of the user who created the operation.
Signed by
The list of accounts that already signed the operation, shown with names and addresses in the expanded view.
Action
Additional actions available for the current user and operation state.
Possible values:
Copy link: Copy a direct link to the operation. The link can be shared with other signers to speed up collaboration.
Reject: Available when the operation can be replaced or canceled.
On this tab, you can view a list of executed and failed operations.
The table structure is similar to the Pending tab and additionally displays the Status column: all operations here are assigned a final status — Success or Failed.
The history view helps trace which actions were executed, by whom, and with which result.
Common use cases
The Queue page helps coordinate multisig actions between several accounts. This section describes common scenarios step by step.
View the operation queue
Review pending operations and see which transaction needs to be executed first.
Go to Queue in the main menu and make sure the Pending tab is selected.
In the This transaction needs to be executed first block, review the first transaction with the smallest Nonce.
Scroll down to the Pending transactions section to see all remaining operations in the queue, ordered by nonce from smallest to largest.
If the queue is empty for the selected network, the There are no transactions yet message appears instead of the table.
Sign transactions
Sign a pending operation so that it can eventually be executed.
Go to Queue in the main menu and make sure the Pending tab is selected.
Locate the operation that requires your signature and verify that:
Not all required signatures are collected.
The Sign action is available, which confirms that you haven't yet signed it and you're authorized to.
Then click Sign.
In the Sign transaction popup, review and verify operation details before signing, and then click Sign.
The Sign action for the corresponding operation will gray out signaling that you've already signed the operation.
If your signature is the last required one, both Sign and Execute actions may be available, allowing you to sign and immediately execute the operation when conditions are met.
Execute transactions
Execute a fully signed operation and send it to the blockchain.
Go to Queue in the main menu and make sure the Pending tab is selected.
Locate the operation you want to execute and verify that:
The required number of signatures is collected.
There are no other pending operations with a smaller Nonce.
The Execute action is available.
Then click Execute.
In the Confirm transaction popup, review the operation details and estimated fee, and then click Execute.
The operation will display the Executing status for some time, and then will be moved from the Pending tab to the History tab.
If your wallet lacks enough funds to cover the fee, the Your connected wallet does not have enough funds to execute this transaction error appears and the Execute button becomes disabled.
Reject or replace transactions
Reject or replace a queued transaction before it's executed.
Go to Queue in the main menu and make sure the Pending tab is selected.
Locate the operation you want to reject, expand the transaction row and click Reject if the option is available.
Choose one of the available options in the popup:
Replace with another transaction: Propose a new transaction with the same nonce. Follow the creation flow in the opened transaction form or reuse an existing transaction from the queue; both the original and replacement transactions then appear as conflicting.
Reject transaction: Create an on‑chain cancellation transaction with the same nonce. Confirm the action in the Reject transaction? popup. After signing, a separate rejection transaction appears in the queue as conflicting and can be executed instead of the original transaction.
Delete from queue: Remove the transaction locally (available when only one transaction with this nonce exists). Confirm your choice in the Delete transaction? popup. A new, empty transaction slot with the same nonce becomes available.
Handle conflicting transactions
Handle several transactions with the same nonce and execute only one of them.
Go to Queue in the main menu.
Identify groups of transactions marked as conflicting, indicated by a message Conflicting transactions. Executing one will automatically replace the others.
Review the details of each conflicting transaction to decide which one should be executed.
Execute the chosen transaction following the steps in Execute transaction.
After the chosen transaction is executed, check that Execute becomes unavailable for other conflicting transactions and that they disappear from the queue.
Batch execution
Execute several fully signed and sequential transactions in a single blockchain transaction.
Go to Queue in the main menu and make sure the Pending tab is selected.
Verify that:
There are multiple transactions in the queue.
All of them are fully signed.
Their nonces form a continuous sequence (for example:
5,6,7).The Execute batch button above the table is available.
Then click Execute batch.
In the Batch execution popup, review a list of transactions to be executed and their details and then click Execute.
The executed transactions will be displayed on the History tab.
View the queue history
Review the history of previously signed and executed operations.
Go to Queue in the main menu.
Switch to the History tab.
Review the list of past operations.
If needed, open the details for a specific operation to see its parameters and the list of signers.
Use filters or sorting (where available) to focus on a particular period, operation type, or status, such as Failed operations that may require attention.
Last updated
Was this helpful?