What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Start with the transaction hash and a receipt lookup, then identify where the transaction stopped. A submission that was rejected or never observed needs a propagation, nonce, balance, or mempool investigation. A transaction that appears in a block with execution_status: REVERTED reached execution and needs a contract-logic and state-effects investigation. Keep that execution result separate from finality_status; a transaction can execute successfully on L2 while still waiting for L1 acceptance.
What a “failed” Starknet transaction can mean
“Failed” is not one protocol state. A wallet may display the same word when a node rejects a submission, when a sequencer has not yet accepted it, when account validation fails, or when an included transaction reverts while calling contracts. Those cases leave different evidence and require different recovery steps.
As an Amazon Associate I earn from qualifying purchases.
Use five lifecycle checkpoints to classify the problem:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Checkpoint | What you are checking | Typical evidence |
|---|---|---|
| Submission and propagation | Did the provider accept and relay the request? | Wallet error, RPC response, or no receipt from the submitting provider |
| Mempool and validation | Will the sequencer keep the transaction and does the account approve it? | Nonce, fee/balance, transaction-validity, or account-validation errors |
| Execution | Did the requested calls complete? | execution_status of SUCCEEDED or REVERTED |
| L2 acceptance | Was the transaction included and accepted on Starknet? | Block information and the receipt’s finality status |
| L1 acceptance | Has the L2 result reached the settlement layer? | A later finality state, not an execution result |
The official Starknet transaction reference defines the lifecycle, receipt fields, transaction types, and version-specific status and mempool behavior. The protocol’s operating-system architecture is described in the SNOS documentation.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Step 1: Collect the facts before retrying
Write down the exact transaction hash, network (for example, mainnet or a test network), wallet or dApp, RPC provider, timestamp, and the complete error text. Do not paraphrase an error that may contain a nonce, fee, calldata, or validation clue. If the wallet shows a “pending” or “failed” banner, preserve a screenshot or copy of the underlying details as well.
The provider matters because status visibility is not universal. A hash can be unknown to one node while another node has received or included it. Always begin with the same provider that accepted the submission, then compare with a second trusted provider only as a propagation check.
Step 2: Query the transaction receipt
Use the JSON-RPC method starknet_getTransactionReceipt with the hash. A raw request has this shape:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems{"jsonrpc":"2.0","method":"starknet_getTransactionReceipt","params":["TRANSACTION_HASH"],"id":1}Replace TRANSACTION_HASH with the exact hexadecimal hash and send the request to the RPC endpoint used by the wallet or application. A receipt is protocol-level evidence, not merely a wallet display. When available, record these fields in a case note:
finality_statusexecution_status, when the transaction has executedactual_fee- block hash and block number
- events and L1 messages
- execution-resource information
If the method returns a not-found or unknown-transaction response, do not conclude that the transaction reverted. It may have been rejected before inclusion, may not have propagated to that node, or may not yet be visible. Keep the wallet/provider error and submission time, and move to the pre-inclusion branch below.
Step 3: Read finality and execution as separate status dimensions
finality_status describes progress through Starknet’s acceptance and settlement lifecycle. execution_status describes the result of execution for a transaction that reached that stage. A transaction can have a successful execution while its finality is still an intermediate state, and waiting for L1 acceptance does not turn a successful execution into a failure.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Use this decision rule:
- Receipt absent: investigate submission, propagation, mempool, nonce, balance, and validation.
- Receipt present with
execution_status: REVERTED: investigate the failing validation or contract call and account for the state effects of a revert. - Receipt present with successful execution but an intermediate
finality_status: treat it as an inclusion/finality wait, not an execution failure.
Status names and lifecycle behavior are release-sensitive. The cited reference discusses the vocabulary in the context of Starknet v0.14.0, so verify the documentation for the network and node version you are using before applying a status or timeout rule.
PC 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 & 11Outdated 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 matchBranch A: the transaction was rejected or is not visible
Check the submitting provider first
Query the original RPC provider and confirm that you are using the correct network. A mainnet hash queried against a testnet endpoint, or the reverse, looks exactly like a missing transaction. If the original provider returns an error immediately, save its code and message; a local wallet message alone may omit the node’s reason.
Then query another provider for the same network. If the second provider sees the transaction, the issue is visibility or propagation at the first provider. If neither sees it and the original submission returned an error, treat it as unaccepted until the provider confirms otherwise. Do not submit repeated replacements merely because one explorer has not indexed the hash.
Verify nonce and account state
Compare the transaction’s nonce with the account’s current nonce on the same network. A stale nonce can be rejected; a future nonce may be held back or refused according to the network’s mempool policy. If another transaction has already consumed the nonce, retrying the old transaction cannot repair that earlier state.
Check the account’s spendable balance for both the call and the maximum fee or fee limit. A balance that covers the transfer but not the fee can fail before execution. Token balances, fee-token availability, and account-specific fee rules should be checked at the current block state, not from a cached wallet screen.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Review validity and mempool constraints
From v0.14.0, sequencers maintain mempools; the precise rules for future nonces, replacement transactions, and expiry are configuration- and release-sensitive. The transaction reference currently describes a transaction time-to-live configured to five minutes in that context. Treat that as a documented setting for the cited version, not as a universal promise for every network or provider.
Check the network’s current documentation for:
- which future nonces may be admitted;
- when a replacement is allowed and what fee-bump rule it uses;
- how long an unconfirmed transaction is retained;
- whether the provider exposes mempool status or only accepted receipts.
If a transaction expires from a mempool, obtain the current nonce and fee conditions before constructing a new one. Do not blindly reuse an old nonce, calldata, or fee limit.
Separate account validation from requested execution for INVOKE
An INVOKE transaction has an account-contract validation phase and a requested execution phase. The account contract’s __validate__ logic decides whether the account approves the transaction; __execute__ initiates the requested calls. Signature checks, nonce checks, fee checks, and custom account rules can therefore reject a transaction before the target contract is called.
This distinction prevents a common misdiagnosis: a dApp call can be correct while the account contract rejects the signature or nonce, and a valid account approval can still be followed by a revert in one of the called contracts. Account contracts define their own validation logic, so a generic wallet remedy is not guaranteed.
Branch B: the receipt says execution_status: REVERTED
Inspect the complete receipt
Record the block hash and number to prove inclusion, then inspect actual_fee, events, L1 messages, and execution resources. Read any revert reason or execution error supplied by the provider, but do not assume there is a universal message-to-fix dictionary: the protocol reference does not define one. A message such as an authorization, balance, deadline, or invariant failure is an application clue that must be interpreted in the context of the called contracts and calldata.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Execution resources can reveal that the transaction reached a resource limit or consumed resources before a later call failed. They are evidence for the provider or dApp team, especially when the visible error text is short.
Understand what a revert changed
A reverted transaction is still included in a block. The account nonce increases, and a fee is charged for resources consumed up to the failure. State changes made during the execution stage are rolled back, so a transfer or storage write that occurred only in that stage should not persist.
Validation-stage changes are not covered by the execution rollback. Events and L1 messages emitted during execution are reverted with that stage, while events may also have been produced during validation or fee charging. For that reason, do not infer “nothing happened” from a revert, and do not promise a fee refund.
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 →Before retrying, read the account’s current nonce and balances again. Because the reverted transaction consumed its nonce, resubmitting the same payload with the old nonce will normally create another rejection rather than replaying the original attempt.
Use the failing condition to choose a correction
- Authorization or signature condition: confirm the connected account, chain identifier, signer, and permissions expected by the contract.
- Insufficient balance or allowance: check the relevant token balance and allowance at the latest state, including the fee token.
- Deadline, price, or slippage condition: refresh the quote or deadline and verify that the calldata still matches the current application state.
- Contract invariant or business-rule failure: inspect the dApp’s documented preconditions and simulate or preview the call if the application provides that feature.
- Resource or fee-limit failure: obtain a current estimate from the wallet or provider and confirm that the account can pay the resulting fee.
These are diagnostic branches, not guarantees. The exact remedy depends on the account contract, target contracts, calldata, and current state.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Transaction-type differences that affect diagnosis
| Type | Where to focus | Common evidence to preserve |
|---|---|---|
INVOKE |
Account __validate__, account __execute__, then each called contract |
Nonce, signature/validation error, calldata, events, messages, and execution resources |
DECLARE |
Class declaration validity, class hash, account validation, and fee payment | Class hash, compiler/declaration details, validation error, receipt status, and fee |
DEPLOY_ACCOUNT |
Account-class validity, constructor inputs, address derivation, validation, and fee | Predicted address, class hash, constructor calldata, nonce, and receipt fields |
The same “failed transaction” label therefore has different likely causes by type. Do not apply an INVOKE-specific account-call explanation to a declaration or account deployment without checking that transaction’s lifecycle.
When the transaction looks stuck
Stuck with no receipt
Confirm the network and original provider, then check whether the provider returned an acceptance response or only accepted the wallet request. Compare the account nonce and balance with the submitted values. If the network uses a mempool, determine whether the transaction is still within the documented retention period and whether a replacement is permitted. A second submission can create a nonce conflict if the first transaction is actually pending.
Included but waiting for finality
If the receipt contains a block and a successful execution result, monitor finality_status rather than resubmitting. L2 inclusion and L1 acceptance are different milestones. A delay at the latter does not undo calls that already executed on L2.
Explorer and wallet disagree
Prefer the receipt returned by the RPC provider for the network you actually used, then compare block and status fields across providers. Indexers can lag, cache old data, or omit execution-resource details. Keep the provider URL, query time, and raw response when opening a support case.
Safe retry procedure
- Classify the first attempt as unobserved/rejected, included and reverted, or included and successfully executed but not final on L1.
- Read the current account nonce and fee-token balance; never assume the failed attempt left them unchanged.
- For a revert, identify and correct the failing precondition before changing the nonce or calldata.
- For a rejected submission, correct the provider, network, nonce, balance, validity, or mempool issue identified by the error.
- Rebuild the transaction with current calldata and fee settings rather than copying a stale serialized request.
- Submit once, save the new hash, and monitor its receipt from the submitting provider.
If the first transaction may still be pending, ask the provider about its state before attempting a replacement. A replacement policy can be version-specific, and an incorrectly chosen nonce can strand both attempts.
What to send to support
Give the wallet, dApp, or RPC provider a compact evidence bundle:
Recommended Free Tools
- network and chain environment;
- transaction hash, if one exists;
- submission timestamp and submitting provider;
- the exact wallet/RPC error;
- raw receipt fields, including both status fields, block data, actual fee, events, messages, and execution resources;
- transaction type and, for an
INVOKE, the account-contract context; - what you tried and whether another transaction has since used the nonce.
Never send a seed phrase, private key, or wallet backup. Support can inspect a transaction and its receipt without those secrets. If a message requests them, use a different official support channel.
A concise decision checklist
- Do I have the exact hash, network, provider, timestamp, and original error?
- Does
starknet_getTransactionReceiptreturn a receipt from the submitting provider? - What are
finality_statusandexecution_status, separately? - If execution reverted, what do the receipt’s fee, events, messages, block, and resource fields show?
- Have I checked the current nonce and fee balance after the attempt?
- For an
INVOKE, could account validation have failed before target-contract execution? - Are mempool, replacement, and expiry rules applicable to this network’s current version?
- Have I avoided retrying until I know whether the original transaction is still pending?
This sequence keeps a propagation problem from being mistaken for a contract bug, and keeps a reverted execution from being mistaken for a transaction that never existed.
Quick Recap
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.
