The swap shows an error but has no transaction hash

No displayed transaction hash means you lack a reliable identifier for the submission. It does not always prove that nothing reached the network. The safest next action depends on the last step you actually completed.

Reconstruct the last confirmed step

• No wallet request appeared: the application may have stopped while finding a quote or opening the wallet.
• You rejected the request: that rejected request should not have produced a newly signed transaction.
• You confirmed on the wallet or hardware device: check account activity before assuming the broadcast failed.
• You signed an offchain order: the application may track an order identifier before any settlement transaction exists.

Ethereum’s transaction documentation distinguishes signing and broadcast from eventual block inclusion. A broken browser response can obscure those stages.

Check evidence outside the swap tab

Use your wallet’s activity panel and the correct network explorer. Search your own public address, verify the time and inspect the newest outgoing transactions. Do not copy a transaction belonging to a similarly named token and assume it is yours.

If an approval confirmed but no swap was signed, return to the quote stage. If a matching swap is pending, manage that transaction instead of creating a new trade. If the application uses private submission, its official status view or support may be needed to establish whether it accepted the transaction.

Document the exact error and approximate time. Support can use those details with your public address; your recovery phrase and private keys do not help diagnose a missing hash. Avoid sending raw signed payloads to strangers because some can still authorize execution.