# Pending or Failed? Check Your Lemon Jet Transaction Find out whether a Lemon Jet transaction is awaiting confirmation, has failed, or is confirmed while a game round or bridge is still pending. Source: https://lemonjet.xyz/blog/lemon-jet-transaction-status Published: 2026-09-05 --- A spinner tells you that something is waiting. It rarely tells you what. If your Lemon Jet transaction is pending, start by identifying the action: an approval, a token transfer, a bridge or a game round. Then check its transaction record. A confirmed transaction can finish one step while the larger action still has work to do. In a [crypto crash game on Base](/blog/crypto-crash-game-on-base), placing a bet and receiving its verified result happen at different points. ## First check whether anything was submitted Open the connected wallet and look for an unanswered confirmation request. A request waiting for your decision has not yet become the transaction you meant to send. Rejecting an unsigned request is different from an onchain failure. If you already confirmed, look for the transaction hash in the wallet or Lemon Jet's Activity view. Use the network shown beside the entry. Base transactions belong on a Base explorer; an Ethereum or Arbitrum transaction needs that network's explorer. If Lemon Jet has no hash, check your wallet's recent activity before trying again. A lost interface response does not establish that nothing was sent. ## Read the status of the specific transaction Lemon Jet's Activity view groups actions with Pending, Confirmed or Failed labels. Open an entry with an explorer link to investigate the underlying transaction. | What you find | What it tells you | Useful next step | | --- | --- | --- | | Wallet confirmation still open | The wallet is awaiting your decision | Review the request | | Submitted transaction without a receipt | Confirmed execution is not established | Check the correct explorer again | | Successful transaction receipt | That particular transaction executed | Identify what action it performed | | Failed transaction receipt | That transaction did not execute successfully | Read its failure reason before retrying | Base's [transaction receipt documentation](https://docs.base.org/base-chain/api-reference/ethereum-json-rpc-api/eth_getTransactionReceipt) explains that receipts become available after inclusion in a block. A missing receipt does not itself describe the final outcome. ## A confirmed approval has not placed your bet LJT use can require an approval before the game transaction. The approval authorises a contract to spend tokens within an allowance; it does not select a multiplier or create a completed round. The same distinction applies when swapping tokens. If the successful record is an approval, check whether the actual swap or game transaction was submitted. Do not interpret an unchanged LJT balance after approval as a missing payout. See [what an LJT approval permits](/blog/ljt-token-approvals) for the complete explanation. ## A confirmed bet can still be awaiting settlement Lemon Jet first records the game transaction and requests randomness. The contract later uses the fulfilled Chainlink VRF request to resolve the round. The starting transaction and the settlement are separate records. Activity can therefore show **Bet placed** as pending even when the initial transaction has succeeded. Once settlement data is available, the entry can show **Bet won** or **Bet lost** and link to the settlement transaction. For verification, follow the round's request and its corresponding result. Chainlink's [VRF security guidance](https://docs.chain.link/vrf/v2-5/security) explains why requests are matched to fulfilments by request ID. Arrival order alone is insufficient. The [Lemon Jet VRF guide](/blog/vrf-explained) covers how to inspect a round. A losing round is a completed game outcome. It does not mean your wallet transaction failed. A delay also does not predict a win, loss or refund. ## A bridge needs a destination result For a [bridge to Base](/blog/swap-vs-bridge-base), source confirmation is only part of the journey. Check the bridge result and receiving transaction instead of relying solely on the outgoing transfer. LI.FI documents pending, completed, partial, refunded and failed outcomes in its [status tracking guide](https://docs.li.fi/introduction/user-flows-and-examples/status-tracking). Read the accompanying details to establish which token, amount and network were involved. A temporary status-service error does not prove that the underlying transfer failed, and a refund must be verified rather than assumed. ## When the record and the interface disagree Check that the wallet address and selected network still match your original action. Then sync the portfolio and reopen Activity. Data services can lag behind the blockchain or temporarily return an incomplete history. If the problem continues, keep the transaction hash, network, approximate time and visible error message for support. Check [network balances and hidden assets](/blog/base-wallet-balances) if the transaction succeeded but you cannot find the received token. Open [Lemon Jet](/app) and check the existing Activity entry before repeating the action. A second submission can create a second transaction. ## FAQ ### Does refreshing the page cancel my transaction? No. Refreshing changes your browser view. It does not cancel an already submitted transaction or reverse a settled round. ### My bet transaction succeeded. Where is the result? Check whether the round has a settlement record. A successful starting transaction confirms placement; the fulfilled VRF request resolves the game. ### Does Failed mean that I lost the round? No. A failed transaction is an execution failure. A losing round is a game that settled with a losing outcome.