Transaction Submission
OrBlock sends transactions through multiple optimized channels to achieve the best performance on the Solana network. Our service routes transactions through self-hosted nodes, staked validator connections, and bundle services to maximize transaction success rates.sendTransaction
OrBlock is a service that supports thesendTransaction Solana RPC method. Simply use our URL where you would place a standard RPC URL. Transactions are intelligently routed through:
- OrbitFlare’s high-performance self-hosted nodes
- Premium staked validator connections
- Bundle services when appropriate
Direct HTTP Endpoints
Amsterdam 🇳🇱:http://ams.orblock.orbitflare.com/?api_key=<api-key>
Frankfurt 🇩🇪: http://fra.orblock.orbitflare.com/?api_key=<api-key>
London 🇬🇧: http://lon.orblock.orbitflare.com/?api_key=<api-key>
New York 🇺🇸: http://ny.orblock.orbitflare.com/?api_key=<api-key>
Tokyo 🇯🇵: http://tok.orblock.orbitflare.com/?api_key=<api-key>
Salt Lake City 🇺🇸: http://slc.orblock.orbitflare.com/?api_key=<api-key>
Secure HTTPS Endpoints
Amsterdam 🇳🇱:https://ams.orblock.orbitflare.com/?api_key=<api-key>
Frankfurt 🇩🇪: https://fra.orblock.orbitflare.com/?api_key=<api-key>
London 🇬🇧: https://lon.orblock.orbitflare.com/?api_key=<api-key>
New York 🇺🇸: https://ny.orblock.orbitflare.com/?api_key=<api-key>
Tokyo 🇯🇵: https://tok.orblock.orbitflare.com/?api_key=<api-key>
Salt Lake City 🇺🇸: https://slc.orblock.orbitflare.com/?api_key=<api-key>
HTTP POST Body
?api_key=<api-key> to create your custom URL for sending transactions.
OrBlock’s regional submission endpoints are strategically placed across Europe (Amsterdam, Frankfurt, London), North America (New York, Salt Lake City), and Asia (Tokyo) to minimize latency worldwide. All nodes run on enterprise-grade hardware with custom optimizations for transaction processing.
Please specify base64 encoding for optimal performance.
Transaction Priority Fee
OrBlock intelligently routes your transaction to the network scheduler. At this point, priority fees matter for processing speed. We recommend setting the compute unit (CU) price to at least1,000,000 for optimal performance, especially during network congestion.
Retries and Confirmations
OrBlock automatically retries transactions until confirmation or expiry. The system will prioritize retries based on:- Transaction priority fee
- Historical success rate of similar transactions
- Current network conditions
Rate Limits
Each API key has an associated rate limit based on your OrbitFlare plan:| Plan | Transactions Per Second (TPS) |
|---|---|
| Starter Orbit | 50 TPS |
| Advanced Nebula | 100 TPS |
| Ultimate Cosmos | 150 TPS |
| OrbitFlare Pass | 300 TPS per location |
Quality of Service
Clients with consistently high transaction failure rates will experience a QoS adjustment to their priority. For example, if only 20% of your transactions successfully land on-chain, your priority may be adjusted accordingly. This is based on your transaction performance over the past 30 minutes.Optimized Routing
What makes OrBlock unique is how it intelligently routes transactions through the Transaction Processing Unit (TPU). Our system analyzes network conditions, validator performance, and transaction characteristics to determine the optimal submission strategy. OrBlock does not simulate transactions by default, which reduces latency. Optional simulation can be enabled through configuration parameters.Front-Running Protection
OrBlock offers optional front-running protection through special submission endpoints. These endpoints utilize optimized bundle services and private transaction pools. Set strict slippage tolerances and calculate minAmountOut values to have additional protection against front-running.Code Examples
CURL
JavaScript
TypeScript
Python
Rust
Go
Jupiter Swap Example
Here’s an example of using OrBlock to execute a Jupiter swap transaction:Contact
For enterprise plans, custom rate limits, and dedicated support, please contact our team:- Email: support@orbitflare.com
- Discord: discord.gg/orbitflare
- Twitter: @orbitflarenodes