Jupiter Swap Pending or Failed? Check Before Retrying

A spinner is not a transaction status

A swap page can keep loading after the wallet or network has moved to another state. The page alone cannot tell you whether a transaction was submitted, succeeded, failed, or is still unresolved. Start by checking what evidence you actually have.

If the wallet is still showing a request and you have not approved it, review that request in the wallet. Do not approve a second unfamiliar prompt just to clear the page. A wallet connection, a transaction signature, and a network result are different things; see how to connect a wallet to Jupiter safely.

If you have a signature, check that exact transaction

Copy the signature from the wallet's own activity or the transaction result—not from an unsolicited message. Open a trusted Solana explorer yourself, choose the same cluster the wallet used, and compare the full signature. Mainnet and Devnet keep separate histories, so a lookup on the wrong cluster cannot answer what happened on the intended one. The Solana transaction-check guide shows what an explorer can and cannot establish.

Read the result as evidence about that transaction, not as a verdict about Jupiter or the token:

• Succeeded: Check the recorded input and output assets, amounts, and fee. Match the mint address and cluster; a ticker or an app spinner is not enough. If the page still says pending, do not repeat the swap just to make its display catch up.
• Failed: Solana executes a transaction's instructions atomically: a failed instruction rolls back the transaction's requested state changes. A network fee may still be charged. Save the signature and any error shown; do not assume the swap completed or that the attempt cost nothing.
• Pending or no result: This is not the same as a confirmed failure. Check the signature and cluster again, allow the explorer or wallet to update, and use another independently opened, trusted source if needed. Solana's status lookup can search only a recent cache unless transaction-history search is requested, so “not found” by itself does not prove that the request never landed.

A transaction can also expire when its recent blockhash is no longer valid. Treat expiration as a distinct outcome, not as a guess based on a spinning screen or a missing explorer result. If the status remains unclear, pause and use Jupiter's official support hub from an address you typed or independently verified. Product-specific retry guidance can change; do not apply a retry count from one Jupiter mode to every wallet or transaction.

Before you decide whether to try again

1. Keep the original signature and confirm the selected cluster. 2. Establish whether the original transaction succeeded, failed, or is reliably known to have expired; a timeout or one empty lookup is not enough. 3. If it succeeded, compare its actual assets and amounts before doing anything else. If it failed or expired, understand the fee and error first. 4. Only if you choose to continue, return to the official app, obtain a fresh quote, and independently review the new wallet request. A new quote can have different conditions. See how to read a Jupiter quote.

Never share a recovery phrase, private key, password, or one-time code with Jupiter support or anyone offering to “unstick” a swap. A transaction signature is public lookup data, but it does not give anyone a reason to ask for wallet secrets or make you sign a verification message. If the domain, cluster, token mint, amount, fee, request, or result does not match what you expected, stop and get help through the official support site.

Practise without a wallet

In this fictional example, a wallet displays signature EXAMPLE-SIGNATURE while the swap page keeps spinning. An explorer opened on Devnet shows no result, but the wallet says the request used Mainnet. What should you do? Select Mainnet and check the same signature before deciding anything; the empty Devnet result says nothing about Mainnet. Do not launch a duplicate swap or share secrets with a stranger.

For the underlying network stages, continue with how Solana transactions work. This guide explains checks, not how to diagnose a live transaction from a screenshot; current wallet, explorer, RPC and Jupiter behavior can vary.