START HERE

A Safe confirmation is not always an on-chain execution. Check the threshold, queue nonce, and execution wallet.

Safe transaction queue decision path for missing confirmations, blocked nonce, and execution readiness.
Original decision diagram. Check the current product interface and policy before acting. Official reference ↗

A signature is not an execution

Safe collects signer confirmations before a transaction is sent on-chain. Open Transactions → Queue in the official Safe interface and compare the number of confirmations with the Safe's required threshold. If the threshold has not been reached, another owner must confirm.

Enough signatures, but still in the queue

Check whether an earlier transaction with a lower Safe nonce is ahead of this one. Safe transactions must use the current nonce; two queued transactions with the same nonce conflict, and executing one invalidates the other. Review the earlier transaction with the owners before replacing or canceling anything.

Ready to execute

A connected signer wallet still needs to submit the execution on-chain; Safe explains why a signer wallet is required. In the basic flow, the executing signer pays the network fee from that signer wallet, not from the Safe balance. Check the actual execution route shown in your Safe interface, since relay or sponsored options may differ. Verify the destination and transaction details again before executing.

Execution submitted but stuck

Open the chain explorer for the executing signer's transaction. If it is pending because of the fee, Safe's help center explains that speed-up happens in the signer wallet. If the transaction failed on-chain, do not blindly retry: inspect the failure and Safe's transaction details. Never share a signer seed phrase or private key.

Official sources

Product interfaces and recovery policies can change. Confirm the current steps before acting.