Free tools Windows power users keep installed
One-click scans. No signup required.
A wallet’s “pending” label does not prove that a Starknet transaction reached the network. Recover safely by locating the exact hash, checking it through an independent Starknet RPC and explorer, confirming the account nonce and fee resources, and only then deciding whether to wait, replace, or submit a fresh transaction. If the operation uses StarkGate, diagnose the bridge stage separately from the DeFi call.
What a “private DeFi transaction” is on Starknet
Privacy tooling does not create a second, invisible Starknet. A private transfer or swap is still a wallet-submitted Starknet transaction. A privacy SDK may use a paymaster so the sender’s information is not exposed in the usual way, and an invoke anonymizer can call an external contract such as a swap executor. The transaction still has a hash, account nonce, fee resources, execution result, and possible mempool lifetime.
As an Amazon Associate I earn from qualifying purchases.
That distinction determines the fix. A missing hash can mean the wallet never obtained admission, a provider cannot see it, or the transaction was evicted. A stuck swap can instead be waiting on an insufficient fee, an invalid nonce, a bridge confirmation, or a contract execution problem. Treat the privacy layer, wallet, Starknet transaction, and any bridge transfer as separate diagnostic layers.
Start with a safe, independent check
Do not speed up, cancel, or resubmit anything until you have the original transaction details. A replacement with the wrong nonce or calldata can create a second failure while the first transaction remains valid.
#1 Best Overall
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
- Copy the exact hash. Get it from the wallet’s transaction details, the DeFi application receipt, or the privacy SDK response. Copy the complete hexadecimal value; do not rely on a shortened activity-list display.
- Confirm the network. Check whether the transaction was sent to Starknet mainnet or a testnet. A mainnet explorer will not show a testnet hash, and the reverse is also true.
- Confirm the account and application. Record the sending account address and the dApp or privacy service that created the call. Make sure the wallet is connected to the same account that signed it.
- Query an independent RPC. Use a trusted Starknet RPC’s
getTransactionStatusmethod for the hash. Do not treat a wallet’s local “pending” label as network confirmation. - Open the same hash in a reputable explorer. Compare the explorer result with the RPC response. A provider outage or indexing delay can make one interface appear empty while another has the receipt.
Starknet.js also exposes getSimulateTransaction. After you have the original transaction data, simulation can reproduce execution and help estimate fees without signing a new transaction. Simulation is diagnostic, not proof that the original transaction was accepted.
Classify the transaction before choosing a fix
Use the RPC response and explorer receipt to place the transaction in one of these states. The action for one state can be harmful in another.
| What you see | What it usually means | Safe next action |
|---|---|---|
| Block and receipt, successful execution | The transaction was included. Check events and the dApp’s expected balance or position. | Wait for the application indexer or UI to update; do not resubmit. |
| Block and receipt, reverted execution | The call reached a block but contract execution failed. State changes from the failed call should not be treated as completed. | Read the revert information and events, then correct the call or application condition before trying again. |
| Rejected response | The node refused the transaction, often before inclusion, because of a nonce, fee, signature, resource, or validation problem. | Fix the reported validation issue and construct a new valid transaction. |
| “Not found” from RPC and explorer | The submission may have been rejected before mempool admission, evicted, or hidden from the provider you selected. | Check nonce and fee state first. Do not blindly submit a replacement. |
| Pending or mempool indication | The transaction may be propagating or waiting for inclusion; a wallet label alone is not authoritative. | Verify nonce, resources, and replacement eligibility, then wait or use the wallet’s documented speed-up flow. |
If the hash is missing or returns “not found”
Rule out a wrong network or wrong hash
Re-copy the hash from the signed transaction record, not from a notification that may contain an application request ID. Select the exact network in both the wallet and explorer. Also check that the account address belongs to the wallet session that submitted the call. Privacy interfaces can show an internal operation identifier in addition to the Starknet transaction hash; only the Starknet hash can be queried by getTransactionStatus.
Recommended Free Tools
Understand why a submitted hash can disappear
A node can reject a transaction before it enters the mempool. A transaction can also be evicted after sitting too long without inclusion. The Starknet v0.14 mempool notes describe a configured five-minute time-to-live for transactions that cannot be included. The peer-to-peer specification also explains that most transactions are included or evicted quickly and that new nodes do not synchronize the existing contents of another node’s mempool. Consequently, a hash that one provider no longer knows about is not proof that the transaction executed.
Provider visibility is another possibility. Query more than one trusted RPC and use an explorer that supports the same network. If every independent check says “not found,” treat the original submission as unconfirmed until nonce inspection proves otherwise.
Rank #2
- Seedless by design, nothing to steal: Your private key is generated inside the EAL6+ chip and never leaves it. No seed phrase is shown or typed at setup, so a tampered device, keylogger, or phishing site has nothing to capture. 9+ years, millions of cards, no known remote hacks.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 16,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Backup without a seed phrase: Your wallet is copied to 2 backup cards with end-to-end encryption, so there are no words on paper to lose or leak. Keep them in separate places; if one card is lost, the others restore full access. Optional seed phrase for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide (4.9 App Store, 4.8 Google Play) - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
Check the account nonce before resubmitting
Read the account’s current nonce and compare it with the nonce in the original transaction. The next usable nonce is account-specific; it is not a global counter and cannot be guessed from the wallet’s activity order. If the account’s state indicates that the original nonce has already been consumed, another transaction may have replaced or superseded the call, so inspect nearby transactions before sending anything. If the original nonce is still unused, you can construct a fresh transaction only after validating its calldata, fee resources, and expected contract state.
Never resubmit the same signed transaction simply because the hash is missing. Starknet.js documents that sending the identical signed transaction with the same nonce is rejected. A fresh submission must be correctly constructed and signed, not a byte-for-byte replay.
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 & 11If the transaction is pending
Check whether it is actually in a block
Use the RPC status and explorer receipt, then look at the latest block number and the transaction’s position. A wallet can retain a pending row after a transaction has been accepted, reverted, or evicted. The receipt and execution status are the authoritative evidence for inclusion and outcome.
Validate nonce, balance, and resource bounds
Starknet version 3 transactions use resource bounds. Depending on account and protocol support, fees can be paid in ETH or STRK. Confirm that the account has enough of the selected fee token and that the transaction’s resource limits are valid for current network conditions. A private swap may also require funds for the swap itself, token approval, and the paymaster arrangement; a fee balance alone does not guarantee that the contract call can complete.
For a new transaction, use the account or library’s fee-estimation path rather than copying limits from an earlier call. The starknet.py documentation describes V3 fee estimation and optional tips; its automatic estimation includes a multiplier intended to absorb fee fluctuations. Preserve the estimated resource fields when signing, and verify which token the account will actually use.
Rank #3
- Seedless by design, nothing to steal: Your private key is generated inside the EAL6+ chip and never leaves it. No seed phrase is shown or typed at setup, so a tampered device, keylogger, or phishing site has nothing to capture. 9+ years, millions of card.
- Tap once to manage your entire crypto wallet across 90 blockchains - no USB cables or Bluetooth, no batteries, no setup. Access 16,100+ coins & tokens, DeFi, NFTs, and staking instantly from your phone
- Backup without a seed phrase: Your wallet is copied to 2 backup cards with end-to-end encryption, so there are no words on paper to lose or leak. Keep them in separate places; if one card is lost, the others restore full access. Optional seed phrase for advanced users.
- Engineered to last up to 25 years: Waterproof (IP69K), shockproof and tested for extreme temperatures from −25°C to 50°C. A durable cold wallet with long‑term protection and independently audited security.
- Trusted by 6 million users worldwide - buy, sell, swap, stake, and spend cryptocurrency directly. The secure offline storage wallet designed for how people actually use crypto wallets
Decide whether waiting is safer than replacing
Wait when the nonce is correct, the transaction is visible to the network, the account has adequate resources, and the fee is competitive enough for current conditions. Do not replace merely because the wallet animation has not changed. If the transaction is close to the documented mempool lifetime and the provider confirms that it remains pending, replacement may be appropriate—but only through a wallet flow that explicitly supports Starknet replacement.
How Starknet replacement works
Replacement is not a universal “cancel” button. A same-account transaction using the same nonce can replace an existing one only under the protocol and wallet rules. Starknet v0.14 mempool notes require the replacement to increase both the tip and the maximum L2 gas price by at least 10 percent. A wallet may apply a larger increase or decline to offer replacement at all.
- Open the original transaction in the wallet and choose its documented Speed up, Replace, or equivalent action, if present.
- Verify that the replacement uses the same account and nonce as the pending transaction.
- Confirm that the wallet increased the tip and maximum L2 gas price by at least the required 10 percent, or by the wallet’s stated higher amount.
- Review the calldata and destination. A speed-up should preserve the intended DeFi operation; never accept an unrelated transaction presented as a cancellation.
- Sign once, then track the new hash independently through RPC and an explorer.
A replacement does not undo a transaction that is already included. If the original becomes accepted first, the replacement can fail because its nonce has been consumed. Never hand-edit calldata, nonce bytes, or resource fields in a signed payload.
When the transaction was evicted
Eviction is a normal mempool outcome, not evidence that funds were lost. If the transaction is absent from independent RPCs and explorers, and the nonce is still available, construct a new transaction from the dApp or privacy SDK rather than replaying the old signature.
- Reconnect the wallet to the correct network and account.
- Reload the dApp so it can obtain current pool, allowance, and contract parameters.
- Recreate the operation and simulate it with
getSimulateTransactionwhen supported. - Estimate fresh V3 resource bounds and choose the correct ETH or STRK fee token.
- Sign the newly constructed transaction and record its new hash immediately.
Before signing, check whether the original call could have changed state despite the missing UI entry. For example, inspect token balances, allowance events, and protocol positions. If the original transaction was included, a second swap or withdrawal could duplicate the action.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- EAL5+ CERTIFIED SECURE ELEMENT + FINGERPRINT PROTECTION — Your private keys stay encrypted offline on a certified EAL5+ chip, the same security tier used in EMV bank cards. Built by DCENT, securing crypto since 2018. Fingerprint authentication adds a second layer no PIN-only wallet can match.
- 10,000+ ASSETS NATIVE ON 100+ BLOCKCHAINS — Hold Bitcoin, Ethereum, XRP, Solana, Cardano, popular stablecoins (USDT, USDC), and NFTs in one wallet. No third-party apps, no fragmented setup — every supported asset works straight out of the box.
- TAP-TO-SIGN MOBILE EXPERIENCE — Pair your wallet with the DCENT mobile app over Bluetooth. Manage tokens, review transactions, and access in-app swap features directly from your phone — no cables, no desktop required.
- WEB3 & dAPP ACCESS VIA METAMASK — Connect to MetaMask and other browser extension wallets to manage NFTs, claim airdrops, and access dApps. A large screen and intuitive 4-button interface keep every transaction clearly visible before you sign.
- SEAMLESS FIRMWARE UPDATES & 30-DAY MONEY-BACK GUARANTEE — Apply security updates without resetting your wallet or migrating funds. Backed by Amazon's 30-day money-back guarantee — your purchase is risk-free.
When the transaction is accepted but the dApp still looks stuck
An included transaction can be successful while the application interface remains stale. Read the receipt’s execution status and events, then verify the resulting token balance or position directly on Starknet. Some privacy flows also have an off-chain relayer or indexer that must process events before the private activity appears in the application.
If execution is reverted, capture the revert reason and event data. Common causes include a changed quote, expired deadline, missing allowance, slippage protection, invalid calldata, or a contract-specific invariant. Do not keep pressing “retry” with the same parameters; obtain a fresh quote and simulate the corrected call first.
Separate StarkGate bridge delays from DeFi failures
If the private DeFi operation depends on moving assets through StarkGate, the bridge has its own lifecycle. A bridge transfer can be waiting even when the DeFi contract call was never submitted, and resubmitting the DeFi call cannot accelerate an L1 confirmation or proof.
| Bridge stage | Meaning | What to check |
|---|---|---|
NOT_RECEIVED |
The bridge service has not yet observed the required L1 deposit. | Open StarkGate’s Activity view, confirm the L1 transaction hash and network, and wait for L1 confirmations. |
ACCEPTED_ON_L2 |
The deposit has been accepted on Starknet. | Verify the L2 token balance and only then retry a DeFi action that depends on those funds. |
| Proof or state-update stage | A withdrawal or cross-chain message is waiting for proof or state synchronization. | Track both L2 initiation and the bridge’s proof status; do not send another withdrawal for the same amount. |
| L1 finalization | The withdrawal still needs final execution on the L1 network after the L2 process. | Wait for finalization and inspect the linked L1 transaction before escalating. |
StarkGate identifies congestion, insufficient gas fees, and proof or cross-chain delays as reasons a transfer can remain pending. Use the Activity tab and its explorer links to determine whether the delay is on L1, L2, or the proof/finalization path.
Privacy-SDK checks that prevent repeat failures
Confirm who submits and pays
A privacy SDK may ask a wallet to sign an invoke transaction while a paymaster supplies fees or changes how sender information is exposed. Verify which account owns the nonce, which account or service pays the fee, and whether the selected fee token is supported. A paymaster failure can prevent submission even though the underlying swap calldata is valid.
Best Value
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
Inspect the anonymizer call chain
Invoke anonymizers can call external contracts such as swap executors. A failure may therefore originate in the anonymizer, the executor, token approval, or the destination protocol. Use simulation and receipt events to identify the failing contract rather than assuming the privacy component itself is broken.
Do not confuse privacy with invisibility
The transaction hash, nonce, fee resources, block inclusion, and contract events remain relevant to recovery. Avoid sharing private notes or identifying data publicly, but provide the technical identifiers that support staff need. Privacy tooling changes how a transaction is funded or routed; it does not remove the need for normal Starknet transaction validation.
A practical decision tree
- Hash found with a successful receipt: stop resubmitting; verify events, balances, and the dApp indexer.
- Hash found with a reverted receipt: read the failure, refresh quote or allowance data, simulate, and submit a corrected call.
- Hash rejected: correct the specific nonce, signature, resource, or fee problem reported by the node.
- Hash pending and visible: confirm nonce and resources; wait or use a supported same-nonce replacement with the required fee increases.
- Hash not found everywhere: check network, nonce, and account state; after confirming the nonce remains unused, create a fresh transaction.
- Bridge status pending: follow StarkGate’s L1 confirmation, L2 acceptance, proof, and finalization stages instead of retrying the DeFi call.
Escalate without exposing wallet secrets
Contact the dApp or wallet’s official support channel when the hash remains ambiguous after independent checks, a replacement fails repeatedly, or a bridge status does not progress. Include:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- the complete transaction hash or hashes;
- network name, account address, and approximate submission time;
- the account nonce and whether the transaction was V3;
- the RPC and explorer results, including any rejection or revert text;
- a concise description of the operation, such as swap, private transfer, deposit, or withdrawal;
- screenshots that show the error without exposing sensitive wallet data.
Never send a seed phrase, private key, wallet password, recovery code, or unrestricted signed message to support. A legitimate support agent can investigate a transaction hash, network, nonce, and calldata summary without taking custody of the wallet.
Quick Recap
Preventing the next stuck transaction
- Copy the hash immediately after signing and save the network alongside it.
- Keep enough ETH or STRK for the selected V3 fee mechanism and understand whether a paymaster is involved.
- Use current fee estimation and resource bounds instead of reusing old limits.
- Record the intended nonce when troubleshooting multiple transactions from one account.
- Keep the bridge transfer hash separate from the later DeFi transaction hash.
- Check contract events and balances after inclusion rather than relying only on the dApp’s activity screen.
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.
