MadeOnSolMade on Sol
Pricing
Get real-time feedsSign in
MadeOnSolMade on Sol

Solana and Robinhood Chain intelligence — KOL wallet tracking, deployer intelligence, all-DEX trade streams, and a developer API. Discover, compare, and build.

Product

  • Solana Data API
  • Robinhood Chain API
  • Robinhood Chain x402
  • MCP Servers & SDKs
  • x402 for AI Agents
  • Agent Intelligence Gateway
  • Pricing
  • Enterprise / For Businesses

Solutions

  • Trading Bots
  • Wallet Tracking
  • Copy Trading
  • Token Scanners
  • Trading Terminals
  • DEX Data
  • Smart Money
  • Token Risk
  • AI Agents
  • ShredPrism Stream
  • View all solutions

Developers

  • API Docs
  • WebSocket Streaming
  • Changelog
  • API Status
  • Latency Benchmarks
  • Data Integrity
  • Data Dictionary
  • Methodology

Resources

  • All Tools
  • Compare Tools
  • Best Trading Bots
  • Best DEXs
  • Best Wallets
  • Best Analytics
  • Best DeFi
  • Best Snipers
  • Blog
  • Blog Archive
  • Signal Scorecard
  • Tool Uptime
  • Community
  • Submit a Tool
  • Advertise

Company

  • About
  • Contact
  • Security
  • Privacy
  • Terms
  • DPA
  • Disclaimer

© 2026 MadeOnSol

MadeOnSol — eenmanszaak, Hulshout, Belgium · KBO/BTW BE 1039.535.538 (art. 56bis, no VAT charged)

Runs on our own dedicated EU servers — self-hosted data stack, own Robinhood Chain node · security

Powered by:constant·k — Private Solana RPC Services
LearnCompute Units

What Are Compute Units on Solana?

TL;DR

Compute units (CU) are Solana’s measure of computational resources consumed by a transaction, similar to gas on Ethereum but with a fixed cap per transaction.

How Compute Units Work

Every Solana transaction has a compute unit budget (default 200,000 CU, max 1.4 million CU per transaction). Each instruction in your transaction consumes CU — simple transfers use very little, while complex DeFi interactions use more. If a transaction exceeds its CU budget, it fails. You can request a higher budget by including a compute budget instruction, but you pay proportionally more in priority fees.

CU and Transaction Fees

Solana’s base fee is fixed (0.000005 SOL per signature), but priority fees are priced per compute unit. The formula is: priority fee = compute units × micro-lamports per CU. Setting a higher compute unit price makes validators prioritize your transaction. During congestion, this bidding mechanism determines which transactions get included. Trading bots dynamically adjust CU price based on network conditions.

Optimizing CU Usage

Request only the CU you need — overestimating wastes money on priority fees. Many bots simulate transactions first to determine exact CU consumption, then set the budget with a small buffer. Lower CU transactions are cheaper and more likely to be included. Jupiter’s routing sometimes finds routes that use fewer CU, saving on fees even if the swap price is slightly less optimal.

Related Tools & Features

Trading Bots
RPC Providers
Developer Tools

Related Terms

Priority Fees & Jito TipsTransaction Fees on SolanaRPC Node
Back to glossary