Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A Stellar DeFi transaction may be waiting to enter a ledger, rejected before inclusion, or included but unsuccessful when its operation runs. Those are different problems with different remedies. Start with the transaction hash and its result in Stellar Lab’s Transaction Dashboard or a suitable Stellar API; a wallet’s spinner or generic error message alone cannot identify the cause.
What does the transaction status actually mean?
Use the transaction hash to locate the record in Stellar Lab’s Transaction Dashboard or an appropriate Stellar API. The dashboard can show the hash, source account, sequence number, processing date, fee, and status. For Soroban transactions, the view may also include contract interactions, events, state changes, resource use, signatures, and fee details. Check that the record is for the intended network, such as mainnet or testnet.
| What you find | What it means | What to inspect next |
|---|---|---|
| Rejected as invalid | Stellar Core did not apply the transaction. An invalid transaction is rejected without consuming the source account’s sequence number or fee, according to Stellar’s Transaction Lifecycle documentation. | Read the returned transaction result for the reason, such as sequence, fee, signature, or validity-window problems. |
| Pending | The transaction has been accepted for propagation but has not yet been confirmed as included in a ledger. An RPC sendTransaction response can report PENDING. |
Check its status again and review its fee, sequence, and time or ledger bounds before deciding whether to submit anything else. |
| Included, but the operation failed | The transaction reached a ledger, but an operation failed during application. The transaction fails and its operations are rolled back. | Inspect the transaction-level result and operation-level error, or Soroban diagnostics for a contract call. |
| Included and successful | The transaction completed on the network. An app may still be showing stale information or may have a separate display or indexing issue. | Compare the ledger record with the app’s activity view and check the app’s own support guidance if they disagree. |
Horizon result codes include categories for bad sequence, insufficient balance, and insufficient fee. An RPC response with ERROR can include an encoded transaction result that explains why Core rejected the submission. Prefer that result over an app’s generic toast or spinner.
Could the fee or Soroban resources be the problem?
Transaction fees are paid in XLM. Classic transactions and Soroban contract transactions do not use identical fee mechanics: a Soroban transaction has an inclusion fee and a resource fee, and it is subject to resource constraints. A fee amount that worked for another transaction is not a guaranteed fix for this one.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- For a Soroban contract transaction, use
simulateTransactionto calculate the resource values and resource fee needed to construct it. - Check the transaction’s fee details and diagnostics, rather than increasing a fee without knowing which fee component is inadequate.
- Inclusion fees may need adjustment during congestion, and network resource limits can change. Consult the current transaction result and the relevant network behavior when preparing a replacement.
Is another transaction or an expired time bound blocking it?
Stellar accounts use sequence numbers to order transactions, and only one sequence for a given account can be consumed per ledger. A stale sequence or another unresolved submission from the same source account can therefore affect a new transaction.
- If the result reports a bad sequence, compare the transaction’s sequence with the source account’s current sequence and any earlier submissions that may have applied.
- If the error is
TRY_AGAIN_LATER, Stellar’s error guidance identifies a case where another transaction from the same source remains in memory after a low-fee rejection. Wait for that transaction to resolve before resubmitting. - Check any time bounds. A transaction submitted outside its allowed time window can be invalid even if its other fields are correct.
Are the network, signatures, XLM balance, or trustline correct?
Check the error against the wallet and asset conditions rather than treating every failure as a fee issue. Stellar CLI troubleshooting guidance describes TxBadAuth as potentially caused by a network-passphrase mismatch or insufficient signature weight. A transaction can also lack enough XLM to cover its fee or encounter a missing trustline.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
- Confirm the wallet is connected to the intended network and that the transaction was built for that network.
- Review the source account’s authorization and signature requirements if the result indicates an authentication problem.
- Check available XLM for the fee and, where the asset requires one, whether the relevant account has the necessary trustline.
Stellar’s disbursement troubleshooting examples also cover missing receiver trustlines, underfunding, and missing accounts. Those are examples from that product’s operations, not proof that the same issue caused a particular DeFi transaction to fail.
When is it safe to resubmit a transaction that still looks stuck?
Do not blindly submit the same transaction again while its status or validity is unclear. Stellar’s Soroban debugging guidance says that a transaction that has not applied within 1–2 minutes is highly unlikely to remain remembered by the network; this is documentation guidance, not a confirmation-time guarantee for every wallet or endpoint.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Look up the original hash and verify whether it was included, rejected, or is still pending.
- Check its time or ledger bounds and whether the validity window has expired.
- If the bound expires without application, prepare a transaction with appropriate client-side time or ledger bounds before resubmitting. If the problem persists, Stellar’s guidance says to consider a fee bump.
Before taking action on a DeFi transaction, also check the application’s instructions: an app may have its own handling for an unfinished swap, contract call, or other operation that is not visible from the network result alone.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What information is needed to diagnose a specific failure?
A general troubleshooting guide cannot establish the right recovery action for an individual transaction without its transaction hash, exact result or displayed error, network, wallet, and DeFi application or contract. Those details identify whether the issue is at submission, ledger inclusion, account authorization, asset setup, or contract execution; the app’s private retry behavior is not established by the public network record.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
