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 matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A larger Solana priority-fee bid can help a transaction rank higher, but the bid alone does not determine its place in the scheduler. For legacy and v0 transactions, the fee is based on the requested compute-unit price multiplied by the requested compute-unit limit. The scheduler separately compares validator reward with an estimated transaction cost. That distinction explains why two transactions paying the same priority fee can still receive different priority.
How the priority fee is calculated
For legacy and v0 transactions, the priority fee is calculated from the requested compute-unit (CU) price and the requested CU limit:
priority_fee_lamports = ceil(CU_price_micro_lamports × requested_CU_limit / 1,000,000)
There are 1,000,000 micro-lamports in one lamport. The formula uses the limit in the transaction, not the number of compute units the transaction actually consumes. Raising the CU price raises the fee at a fixed limit; raising the limit can also raise it, even if execution uses less compute. The transaction’s total fee also includes its base fee, and Solana charges fees even when a transaction fails. Solana’s fee structure documentation describes these calculations.
#1 Best Overall
For example, requesting 500,000 CUs at 2 micro-lamports per CU produces a 1-lamport priority fee under this formula. This is an arithmetic illustration, not a live quote or recommended bid.
V1 uses a different fee configuration
Do not apply the legacy/v0 formula to the v1 message format. V1 configures the priority fee as an absolute total in lamports in the message; Compute Budget instructions do not configure v1 transactions. See the fee structure documentation and compute-budget documentation.
Rank #2
- Solana Crypto Solana Cryptocurrency
- Solana Crypto Solana Cryptocurrency
- Hardcover journal with 240 line-ruled pages (120 sheets)
- Built-in elastic closure and ribbon bookmark
- Includes an expandable inner storage pocket and a pen holder
Why a higher bid does not guarantee higher rank
Solana documents scheduler priority as:
Priority = reward × 1,000,000 / (cost + 1)
Reward includes the priority fee and the non-burned portion of the base fee. The documented base fee is 5,000 lamports per signature; half is burned and half goes to the validator. Cost is a separate scheduler estimate, not the requested CU limit used in the priority-fee multiplication. Its documented components include signature work, writable-account locks, instruction data, program execution, and loaded account data. The multiplier preserves precision, while adding one prevents division by zero. The formulas are documented in Solana’s fee structure and compute-budget references.
In practical terms, a larger priority fee can increase reward, but scheduler priority is a reward-to-estimated-cost ratio. Transactions with the same priority-fee amount may therefore have different priority ratios if their estimated costs differ. Priority determines dequeue order from the scheduler’s buffer; it does not guarantee that a transaction will land. Inclusion is competitive, and fee conditions change with network activity.
Rank #3
- Solana Crypto Solana Cryptocurrency
- Solana Crypto Solana Cryptocurrency
- Hardcover journal with 240 line-ruled pages (120 sheets)
- Built-in elastic closure and ribbon bookmark
- Includes an expandable inner storage pocket and a pen holder
Set the compute limit from measured usage
A limit that is much higher than the transaction needs can increase the legacy/v0 priority fee without improving execution. Solana’s documented defaults for those formats are 200,000 CUs per non-builtin instruction and 3,000 CUs per builtin instruction, subject to a maximum of 1,400,000 CUs per transaction. These are current documented protocol values, not permanent constants. Solana recommends simulating the transaction, then adding a 10% safety margin to observed CU use. Its terminology guidance states, “Transactions should request the minimum amount of compute units required to execute to minimize fees.”
- Simulate the transaction to observe its compute-unit use.
- Set a limit close to measured use, adding Solana’s recommended 10% safety margin.
- Choose a CU price for a legacy/v0 transaction based on current conditions and the priority you need; remember that the price is multiplied by the requested limit.
Solana documents the default limits and simulation guidance in its compute-budget reference, and the quoted guidance in its terminology reference.
Rank #4
- 🪙 Compact and Sleek Design: Measuring 1.57 inches in diameter and 0.12 inches thick, this gold-plated coin is the perfect size for display or carrying as a token of Solana’s blockchain innovation.
- ✨ Gold-Plated Finish: Crafted with a radiant gold-plated coating that exudes elegance and durability.
- 💡 Iconic Solana Logo: One side features the recognizable Solana emblem, symbolizing decentralized technology and progress.
- 🔄 Geometric Pattern Design: The reverse boasts an intricate geometric design, reflecting the precision and beauty of blockchain technology.
- 🛡️ Protective Plastic Case: Includes a clear coin case to shield against scratches, dust, and fingerprints, keeping your collectible pristine.
Use recent fee data as an estimate, not a promise
Solana’s exchange guidance recommends querying getRecentPrioritizationFees with the public keys of the accounts the transaction will write-lock. Account scope matters: transactions touching the same writable accounts can encounter different fee conditions from transactions operating elsewhere. An unscoped query can return the lowest fee needed to land in a recent block, which is often zero. The result reflects recent account-level minimum-fee information; it cannot predict future competition or guarantee inclusion. Treat it as an input to a bidding strategy rather than a quote. See Solana’s exchange integration guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Solana’s production-readiness documentation lists Helius Priority Fee API, QuickNode Priority Fee Add-on, and Triton Priority Fees API as examples of provider APIs. This is a list of examples, not an endorsement. Production-readiness guidance has the details.
Quick Recap
What to compare when evaluating two bids
- Total priority fee: For legacy/v0, compare CU price multiplied by requested limit; for v1, compare the configured absolute lamport fee.
- Limit versus expected use: Check whether the requested limit reflects simulation plus a suitable margin or pays for excess capacity.
- Estimated cost drivers: Consider signatures, writable-account locks, instruction-data size, program execution, and loaded account data.
- Account overlap and current demand: Fee conditions can differ depending on which writable accounts transactions share and what other transactions are competing for them.
- Transaction format: Legacy/v0 Compute Budget instructions and v1 message fee configuration are different mechanisms.
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.
