<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[BlockRazor Blog]]></title><description><![CDATA[Explore BlockRazor product updates, technical tutorials, and insights into blockchain infrastructure for developers and Web3 teams.]]></description><link>https://blockrazor.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6ae33f45a689abae0d3f2bea/65b6e8f3-fdf4-4551-889a-183cef464eae.png</url><title>BlockRazor Blog</title><link>https://blockrazor.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 18:55:33 GMT</lastBuildDate><atom:link href="https://blockrazor.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Base Transaction Benchmark: BlockRazor Achieves a 67.75% Inclusion Win Rate]]></title><description><![CDATA[Base transaction submission benchmark: BlockRazor achieved a 67.75% inclusion win rate vs the official Sequencer in 1,200 same-nonce races.]]></description><link>https://blockrazor.hashnode.dev/base-transaction-benchmark-blockrazor-achieves-a-67-75-inclusion-win-rate</link><guid isPermaLink="true">https://blockrazor.hashnode.dev/base-transaction-benchmark-blockrazor-achieves-a-67-75-inclusion-win-rate</guid><category><![CDATA[Benchmark]]></category><category><![CDATA[base]]></category><category><![CDATA[Transaction Submission]]></category><category><![CDATA[#sequencer]]></category><dc:creator><![CDATA[luvsreal1994]]></dc:creator><pubDate>Mon, 09 Nov 2026 06:45:05 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/021f4226-30ef-4929-9092-ac8231e589e0.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Base's <strong>Denim</strong> upgrade reduced the native block interval from 2 seconds to <strong>200ms</strong>, tightening the window for transaction delivery. For teams running arbitrage, liquidation, and market-making strategies on Base, timely inclusion is an important measure of a submission service. See the <a href="https://docs.base.org/upgrades/denim/200ms-blocks"><u>official native block specification</u></a> and <a href="https://github.com/base/base/releases/tag/v1.5.1"><u>v1.5.1 release notes</u></a> for upgrade details.</p>
<p>To show how BlockRazor performs across different times of day, we ran same-nonce transaction submission tests from a single client in Virginia, USA. This article focuses on inclusion results for BlockRazor and Base's official Sequencer. The test comprised <strong>12 runs starting every 2 hours, with 100 races per run</strong>.</p>
<p>Across all <strong>1,200 races</strong>, <strong>BlockRazor Virginia won 813, achieving a 67.75% inclusion win rate</strong>. Base's official Sequencer won 387 (32.25%). BlockRazor led in <strong>9 of 12 runs</strong>, securing more than two-thirds of the winning inclusions.</p>
<h2><strong>Benchmark Setup: 12 Runs Every 2 Hours</strong></h2>
<p>This article presents results for the following transaction submission paths on <strong>Base Mainnet (Chain ID</strong> <code>8453</code><strong>)</strong>:</p>
<table>
<thead>
<tr>
<th align="left"><strong>Submission Path</strong></th>
<th align="left"><strong>Endpoint Tested</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left"><strong>BlockRazor Virginia</strong></td>
<td align="left"><a href="https://virginia-base.blockrazor.io:10101/eth_sendRawTransaction"><code>https://virginia-base.blockrazor.io:10101/eth_sendRawTransaction</code></a></td>
</tr>
<tr>
<td align="left"><strong>Base Official Sequencer</strong></td>
<td align="left"><a href="https://mainnet-sequencer.base.org"><code>https://mainnet-sequencer.base.org</code></a></td>
</tr>
</tbody></table>
<p>The test took place on <strong>November 7–8, 2026</strong>. Each run included <strong>100 races</strong>, with a <strong>2-second cooldown</strong> configured between races. Runs started at <strong>2-hour intervals</strong>, with <strong>22 hours</strong> between the first and last starts.</p>
<ul>
<li><strong>Test size:</strong> 12 runs and 1,200 races.</li>
<li><strong>Winner determination:</strong> 1,200 successful transaction receipts, checked through Base's official public node at <a href="https://mainnet.base.org"><code>https://mainnet.base.org</code></a>.</li>
<li><strong>Round-start block range:</strong> <code>54,361,773–54,758,811</code>.</li>
<li><strong>Winning inclusion block range:</strong> <code>54,361,775–54,758,813</code>.</li>
</ul>
<h3><strong>Microsecond Submission Timing: Comparing Request Start Order</strong></h3>
<p>To verify synchronized submission, we compared the <strong>client-side request start times for BlockRazor and the official Sequencer in each of the 1,200 races</strong>. We measured the absolute difference between their request start times:</p>
<table>
<thead>
<tr>
<th align="left"><strong>Submission Timing Metric</strong></th>
<th align="right"><strong>BlockRazor–Sequencer Request Start Difference</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left"><strong>P50 (median)</strong></td>
<td align="right"><strong>4 μs</strong></td>
</tr>
<tr>
<td align="left"><strong>P90</strong></td>
<td align="right"><strong>30 μs</strong></td>
</tr>
<tr>
<td align="left"><strong>Maximum</strong></td>
<td align="right"><strong>67 μs</strong></td>
</tr>
</tbody></table>
<p>The submission order did not consistently put BlockRazor first. Among the <strong>1,083 races with distinguishable request start times</strong>, BlockRazor started earlier <strong>552 times</strong>, and the official Sequencer started earlier <strong>531 times</strong>. Another <strong>117 races</strong> had simultaneous starts at microsecond precision.</p>
<p>In the <strong>531 races where the official Sequencer started its request before BlockRazor</strong>, <strong>BlockRazor still won 371 times</strong>. These results demonstrate winning inclusion even when the Sequencer's request started earlier; BlockRazor's wins did not require a fixed first-start advantage.</p>
<h2><strong>Methodology: Same Nonce, Matched Fees, Onchain Winners</strong></h2>
<p>In each race, the tested routes submitted transactions using the <strong>same sender and nonce</strong>. A nonce can be consumed only once on the canonical chain. We matched the transaction hash in the successful receipt to its submission route to determine the winner.</p>
<p>To help users compare transaction delivery under matched fee conditions, we applied consistent parameters for the compared transactions:</p>
<ol>
<li><strong>Matched transactions and fees:</strong> each race used the same sender, recipient, nonce, chain ID, value, empty calldata, and fee parameters. All transactions were EIP-1559 Type 2 zero-value transfers, with <code>maxPriorityFeePerGas</code> fixed at <strong>1,000,000 wei (0.001 gwei)</strong>.</li>
<li><strong>Identifiable transaction hashes:</strong> gas limits distinguished the transactions: <strong>30,000</strong> for BlockRazor and <strong>30,002</strong> for the Sequencer. Every winning receipt used <strong>21,000 gas</strong> and returned <code>status=1</code>.</li>
<li><strong>Concurrent submission:</strong> the client submitted transactions concurrently, allowing them to compete for inclusion with the same nonce and fees.</li>
</ol>
<h2><strong>Overall Results: BlockRazor Won 813 Races at 67.75%</strong></h2>
<table>
<thead>
<tr>
<th align="left"><strong>Submission Path</strong></th>
<th align="right"><strong>Races Won</strong></th>
<th align="right"><strong>Inclusion Win Rate</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left"><strong>BlockRazor Virginia</strong></td>
<td align="right"><strong>813</strong></td>
<td align="right"><strong>67.75%</strong></td>
</tr>
<tr>
<td align="left">Base Official Sequencer</td>
<td align="right">387</td>
<td align="right">32.25%</td>
</tr>
<tr>
<td align="left"><strong>Total</strong></td>
<td align="right"><strong>1,200</strong></td>
<td align="right"><strong>100.00%</strong></td>
</tr>
</tbody></table>
<p>With the same nonce and matched fees, BlockRazor won more than twice as many races as the official Sequencer. For teams focused on execution efficiency, this result demonstrates BlockRazor's transaction delivery competitiveness in this Base Mainnet test.</p>
<h2><strong>All 12 Runs: BlockRazor Led in 9</strong></h2>
<p>Each run contains <strong>100 races</strong>, so each percentage also equals the number of races won. <code>T+00h</code> marks the first run's start; subsequent runs are ordered by their start interval relative to that point.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Run</strong></th>
<th align="left"><strong>Time Since First Start</strong></th>
<th align="right"><strong>BlockRazor</strong></th>
<th align="right"><strong>Sequencer</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">01</td>
<td align="left">T+00h</td>
<td align="right"><strong>72%</strong></td>
<td align="right">28%</td>
</tr>
<tr>
<td align="left">02</td>
<td align="left">T+02h</td>
<td align="right"><strong>91%</strong></td>
<td align="right">9%</td>
</tr>
<tr>
<td align="left">03</td>
<td align="left">T+04h</td>
<td align="right"><strong>48%</strong></td>
<td align="right">52%</td>
</tr>
<tr>
<td align="left">04</td>
<td align="left">T+06h</td>
<td align="right"><strong>100%</strong></td>
<td align="right">0%</td>
</tr>
<tr>
<td align="left">05</td>
<td align="left">T+08h</td>
<td align="right"><strong>47%</strong></td>
<td align="right">53%</td>
</tr>
<tr>
<td align="left">06</td>
<td align="left">T+10h</td>
<td align="right"><strong>83%</strong></td>
<td align="right">17%</td>
</tr>
<tr>
<td align="left">07</td>
<td align="left">T+12h</td>
<td align="right"><strong>66%</strong></td>
<td align="right">34%</td>
</tr>
<tr>
<td align="left">08</td>
<td align="left">T+14h</td>
<td align="right"><strong>62%</strong></td>
<td align="right">38%</td>
</tr>
<tr>
<td align="left">09</td>
<td align="left">T+16h</td>
<td align="right"><strong>57%</strong></td>
<td align="right">43%</td>
</tr>
<tr>
<td align="left">10</td>
<td align="left">T+18h</td>
<td align="right"><strong>31%</strong></td>
<td align="right">69%</td>
</tr>
<tr>
<td align="left">11</td>
<td align="left">T+20h</td>
<td align="right"><strong>68%</strong></td>
<td align="right">32%</td>
</tr>
<tr>
<td align="left">12</td>
<td align="left">T+22h</td>
<td align="right"><strong>88%</strong></td>
<td align="right">12%</td>
</tr>
<tr>
<td align="left"><strong>Total / pooled rate</strong></td>
<td align="left"><strong>1,200 races</strong></td>
<td align="right"><strong>813 / 67.75%</strong></td>
<td align="right"><strong>387 / 32.25%</strong></td>
</tr>
</tbody></table>
<p>BlockRazor led in <strong>9 runs</strong>, reaching <strong>100% in run 4</strong>, <strong>91% in run 2</strong>, and <strong>88% in run 12</strong>. The official Sequencer won more races in runs 3, 5, and 10. All 12 runs contribute to BlockRazor's <strong>67.75% overall inclusion win rate</strong>.</p>
<h2><strong>Evaluate Base Transaction Delivery Through Onchain Results</strong></h2>
<p>For strategies that depend on timely inclusion, a submission service's value ultimately needs to appear in onchain execution results. Across 12 test windows and 1,200 races, BlockRazor delivered <strong>813 wins, a 67.75% overall win rate, and a lead in 9 test windows</strong> under matched priority fees.</p>
<p>We welcome teams running arbitrage, liquidation, and market-making strategies on Base to try BlockRazor with their own transaction workloads and fee policies, and evaluate execution in their deployment environments.</p>
<ul>
<li>Read the <a href="https://docs.blockrazor.io/transaction-submission/transaction-sending/base/eth_sendrawtransaction"><u>BlockRazor Base Transaction Submission Configuration Guide</u></a>.</li>
<li>Join the <a href="https://discord.gg/qqJuwRb8Nh"><u>BlockRazor Discord community</u></a> for technical support and test access.</li>
</ul>
]]></content:encoded></item><item><title><![CDATA[Blockchain Edge Fabric]]></title><description><![CDATA[This section introduces BlockRazor's core technology, Blockchain Edge Fabric, including its core concepts, architectural components, target user, and role…]]></description><link>https://blockrazor.hashnode.dev/blockchain-edge-fabric</link><guid isPermaLink="true">https://blockrazor.hashnode.dev/blockchain-edge-fabric</guid><dc:creator><![CDATA[luvsreal1994]]></dc:creator><pubDate>Thu, 05 Nov 2026 07:55:02 GMT</pubDate><content:encoded><![CDATA[<p>This section introduces BlockRazor's core technology, Blockchain Edge Fabric, including its core concepts, architectural components, target user, and role within the product ecosystem</p>
<p>Blockchain Edge Fabric (BEF) is BlockRazor’s blockchain-native edge infrastructure system built for high-performance blockchain propagation scenarios.</p>
<p>The core of BEF is not merely shorter network paths or higher bandwidth. Instead, it is a multilayer optimization system built around the structure, timeliness, propagation behavior, and critical processing paths of blockchain data itself, specifically for the transmission of transactions, blocks, and on-chain signals.</p>
<p>In blockchain networks, data propagation has clear chain-native characteristics: transactions and blocks have unique identifiers, dependency relationships, time-sensitive windows, repeated propagation, priority differences, and role-specific paths. If a propagation system understands such data only from the perspective of the general network layer, it is difficult to achieve stable advantages in highly competitive environments.</p>
<p>BEF integrates blockchain data modeling, customized data transmission strategies, blockchain propagation logic, topology intelligence, edge access, and real-time feedback into a unified infrastructure architecture. Its goal is to enable BlockRazor’s products and services to handle critical on-chain data flows with lower latency, lower jitter, and more predictable performance.</p>
<h3><strong>Core Concept</strong></h3>
<p>BEF is designed around one central judgment: blockchain propagation is not a generic data transmission problem, but a system engineering problem involving data awareness, protocol awareness, and path awareness.</p>
<p>For professional on-chain participants, the key factors that affect propagation performance include:</p>
<ul>
<li>Whether data can be quickly identified, split, deduplicated, and scheduled</li>
<li>Whether critical data can be prioritized into effective propagation paths</li>
<li>Whether transmission strategies understand the structural differences between transactions, blocks, and on-chain signals</li>
<li>Whether data can avoid low-quality nodes, congested paths, and ineffective duplicate forwarding</li>
<li>Whether the system can adjust propagation strategies based on real-time network conditions</li>
<li>Whether stable performance can still be maintained under high load and intense competition</li>
</ul>
<p>BEF is not a single network resource, but an engineering system dedicated to continuously optimizing critical on-chain propagation paths.</p>
<h3><strong>Architecture Components</strong></h3>
<p>BEF is built on four core capabilities:</p>
<ul>
<li>Blockchain data awareness</li>
<li>Customized data transmission strategies</li>
<li>Topology and path intelligence</li>
<li>Real-time feedback and adaptive optimization</li>
</ul>
<p>These capabilities work together to enable system-level optimization tailored to the unique nature of blockchain data propagation, rather than relying solely on general-purpose network acceleration.</p>
<h4><strong>Blockchain Data Awareness</strong></h4>
<p>Blockchain data is not ordinary request traffic.</p>
<p>Transactions, blocks, bundles, state-related signals, and other on-chain data objects typically have clear identities, propagation priorities, time sensitivity, and upstream/downstream dependency relationships. BEF builds data awareness around these characteristics, enabling the system to understand the value and handling requirements of different data objects during propagation.</p>
<p>This data awareness is the foundation of BEF. It allows the propagation system to decide how data should be encoded, scheduled, forwarded, and confirmed based on data type, timeliness, duplication level, dependency relationships, and target path, rather than treating all on-chain data as ordinary network packets.</p>
<h4><strong>Customized Data Transmission Strategies</strong></h4>
<p>One of BEF’s key technical directions is to customize data transmission strategies according to the characteristics of blockchain data.</p>
<p>Blockchain propagation often involves high-frequency small messages, large block payloads, duplicated data, short-lived signals, and concurrent multi-path propagation. BEF designs transmission logic around these traits, including data sharding, priority queues, deduplication, batching, incremental transmission, retransmission control, congestion awareness, and propagation scheduling.</p>
<p>The goal of these strategies is not simply to increase throughput, but to reduce ineffective transmission, shorten propagation wait times, and allow critical data to enter effective processing paths faster in competitive on-chain environments.</p>
<p>BEF co-designs data transmission strategies with blockchain propagation logic, allowing the system to choose more suitable encoding, scheduling, forwarding, and confirmation methods based on the structure, timeliness, and propagation state of transactions, blocks, and on-chain signals.</p>
<h4><strong>Topology and Path Intelligence</strong></h4>
<p>Not all nodes in a blockchain network have equal propagation value.</p>
<p>Different nodes, regions, roles, and connection states can all affect the speed and effectiveness of on-chain data dissemination. BEF continuously evaluates network topology, node quality, path stability, and critical processing entry points in order to select path combinations with higher propagation value.</p>
<p>This path intelligence is not simply about choosing a faster route in the traditional sense. It dynamically determines where data should enter, which paths it should traverse, and which destinations it should reach first by combining participant distribution, node response quality, data propagation state, and the target chain’s processing path.</p>
<p>BEF focuses on the effectiveness of on-chain propagation paths, not merely physical distance.</p>
<h4><strong>Real-Time Feedback and Adaptive Optimization</strong></h4>
<p>Blockchain networks are in constant change.</p>
<p>Node status, network load, propagation speed, congestion conditions, data duplication rates, and path quality all change over time. Through real-time telemetry and feedback mechanisms, BEF continuously observes propagation performance and uses these signals to optimize routing, scheduling, and transmission strategies.</p>
<p>This feedback mechanism allows BEF to keep learning from historical performance and real-time conditions, reducing dependence on fixed paths and static configurations. In high-concurrency, high-frequency, and highly competitive environments, this adaptive capability is essential for maintaining stable propagation performance.</p>
<h3><strong>For Professional On-Chain Participants</strong></h3>
<p>BEF is built for professional participants who are highly sensitive to on-chain data speed, stability, and execution timing, including:</p>
<ul>
<li>Searchers and MEV teams</li>
<li>Validators and node operators</li>
<li>Wallet and dApp teams</li>
<li>Trading firms and market makers</li>
<li>Infrastructure teams building low-latency on-chain products</li>
</ul>
<p>These teams care not just about whether they can connect to the chain, but whether they can obtain effective data earlier, submit critical transactions faster, reach processing entry points more reliably, and achieve more predictable network performance in competitive environments.</p>
<h3><strong>Relationship to the BlockRazor Product Ecosystem</strong></h3>
<p>BEF is the shared infrastructure layer behind multiple BlockRazor products and services.</p>
<p>Different products may expose different interfaces, workflows, and functional forms based on BEF, but they share the same underlying capabilities: blockchain data awareness, customized data transmission strategies, topology intelligence, edge access, and real-time adaptive optimization.</p>
<p>When a product or service is described as “powered by BEF,” it means that it inherits BEF’s underlying capabilities in high-performance blockchain propagation, rather than merely relying on a single node, interface, or network path.</p>
<h3><strong>Conclusion</strong></h3>
<p>The value of BEF lies in elevating blockchain propagation from a “connectivity problem” to a “systems optimization problem.”</p>
<p>By continuously modeling data structure, propagation paths, node quality, and real-time network conditions, BEF provides BlockRazor’s products and services with a reusable, evolvable, and difficult-to-replicate foundation of performance capability that cannot be reproduced through isolated resources alone.</p>
]]></content:encoded></item><item><title><![CDATA[Robinhood Chain Feed and Transaction Benchmark: BlockRazor vs bloXroute]]></title><description><![CDATA[Source: To measure Robinhood Chain infrastructure across a complete latency-sensitive workflow, we benchmarked BlockRazor against bloXroute on both block…]]></description><link>https://blockrazor.hashnode.dev/robinhood-chain-feed-and-transaction-benchmark-blockrazor-vs-bloxroute</link><guid isPermaLink="true">https://blockrazor.hashnode.dev/robinhood-chain-feed-and-transaction-benchmark-blockrazor-vs-bloxroute</guid><dc:creator><![CDATA[luvsreal1994]]></dc:creator><pubDate>Thu, 05 Nov 2026 07:48:43 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/7efc3814-d8fe-4378-ab8e-11d7dc4f585c.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Source: <a href="https://blockrazor.io/blog/robinhood-feed-blockrazor-vs-bloxroute-benchmark/"><u>https://blockrazor.io/blog/robinhood-feed-blockrazor-vs-bloxroute-benchmark/</u></a></p>
<p>To measure Robinhood Chain infrastructure across a complete latency-sensitive workflow, we benchmarked BlockRazor against bloXroute on both block reception and transaction submission. The Feed comparison used the Robinhood Chain Node-required Sequencer Feed included with BlockRazor Package and the Robinhood Chain Sequencer Feed available in bloXroute Enterprise. BlockRazor Feed arrived first on all 2,919 consecutive matched blocks from <code>94,990,680</code> through <code>94,993,598</code>, leading by <code>8.264 ms</code> at P50 and <code>24.520 ms</code> at P99. In two one-to-one, 100-round submission tests, BlockRazor won 99 same-nonce races and 98 distinct-nonce onchain-position comparisons.</p>
<blockquote>
<p><strong>Key results</strong></p>
<ul>
<li>Feed comparison: BlockRazor Package Node-required Sequencer Feed vs bloXroute Enterprise Sequencer Feed.</li>
<li>Feed result: BlockRazor arrived first on 2,919/2,919 matched blocks, leading by <code>8.264 ms</code> at P50 and <code>24.520 ms</code> at P99.</li>
<li>Same nonce: BlockRazor won 99/100 rounds; bloXroute won 1/100.</li>
<li>Distinct nonces: BlockRazor won 98/100 rounds; bloXroute won 2/100.</li>
<li>RPC response: In the same-nonce test, BlockRazor and bloXroute averaged <code>0.504 ms</code> and <code>13.769 ms</code> in <code>sendDuration</code>. In the distinct-nonce test, they averaged <code>0.447 ms</code> and <code>12.797 ms</code>.</li>
<li>Scope: RPC response speed and final onchain ordering are different metrics and should not be used interchangeably.</li>
</ul>
</blockquote>
<h2><strong>Test scope and interpretation</strong></h2>
<p>The Feed test matched the two Robinhood Chain Sequencer Feeds by block height. The BlockRazor side used the Node-required Feed included with BlockRazor Package; the bloXroute side used the Sequencer Feed available in bloXroute Enterprise. For each matched block, the feed that became client-ready first was represented as <code>0.000 ms</code>; the other value is the difference between the two arrival timestamps, not absolute end-to-end latency.</p>
<p>We ran the transaction-submission tests on Robinhood Mainnet (Chain ID <code>4663</code>). Each test covered 100 rounds with a two-second cooldown in a one-to-one configuration: the BlockRazor Ohio relay against the bloXroute Robinhood API (<a href="https://api.blxrbdn.com"><code>https://api.blxrbdn.com</code></a>, method <code>robinhood_tx</code>). The same-nonce rounds started across blocks <code>95,095,809–95,097,852</code>; the distinct-nonce rounds started across blocks <code>95,098,135–95,100,229</code>.</p>
<p>The same-nonce winner was the only transaction successfully included for that nonce. The distinct-nonce test allowed both transactions to be included, comparing block height first and then the lower Transaction Index when they landed in the same block.</p>
<p>Client hardware, network routes, endpoint deployment, concurrent load, and timestamp implementation can all affect the measurements. We therefore scope these findings to this test window and configuration, and recommend repeating the A/B test from your own production region and transaction path.</p>
<h2><strong>Node-required Feed vs Enterprise Sequencer Feed: BlockRazor arrived first</strong></h2>
<table>
<thead>
<tr>
<th align="left"><strong>Source</strong></th>
<th align="right"><strong>Samples</strong></th>
<th align="right"><strong>First-arrival rate</strong></th>
<th align="right"><strong>P50</strong></th>
<th align="right"><strong>P90</strong></th>
<th align="right"><strong>P95</strong></th>
<th align="right"><strong>P99</strong></th>
<th align="right"><strong>Max</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">BlockRazor Node-required Feed (Package)</td>
<td align="right">2,919</td>
<td align="right">100.00%</td>
<td align="right">0.000 ms</td>
<td align="right">0.000 ms</td>
<td align="right">0.000 ms</td>
<td align="right">0.000 ms</td>
<td align="right">0.000 ms</td>
</tr>
<tr>
<td align="left">bloXroute Sequencer Feed (Enterprise)</td>
<td align="right">2,919</td>
<td align="right">0.00%</td>
<td align="right">8.264 ms</td>
<td align="right">17.151 ms</td>
<td align="right">20.526 ms</td>
<td align="right">24.520 ms</td>
<td align="right">46.577 ms</td>
</tr>
</tbody></table>
<p>Across this continuous sample, our relative lead increased from <code>8.264 ms</code> at P50 to <code>24.520 ms</code> at P99, with a maximum observed difference of <code>46.577 ms</code>. These values are paired arrival gaps between the feeds; they do not mean that BlockRazor's full delivery path took zero time.</p>
<p><a href="https://docs.blockrazor.io/streams/node-stream/robinhood-chain/sequencer-feed"><u>BlockRazor Robinhood Chain Node-required Sequencer Feed</u></a> is included with BlockRazor Package and delivers sequential ordered blocks through a compatible local node. This benchmark compares it with the Robinhood Chain Sequencer Feed in bloXroute Enterprise and focuses on when data became client-ready; it does not compare every feature, quota, or commercial term in the two plans.</p>
<h2><strong>Transaction benchmark 1: Same-nonce races</strong></h2>
<p>For the same-nonce test, we used one sender and the same nonce while submitting distinguishable transactions through BlockRazor and bloXroute. At most one transaction per round could consume that nonce, making this a test of which route entered Sequencer ordering first.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Submission route</strong></th>
<th align="right"><strong>Winning rounds</strong></th>
<th align="right"><strong>Win rate</strong></th>
<th align="right"><strong>Average RPC response</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left"><strong>BlockRazor Ohio relay</strong></td>
<td align="right"><strong>99</strong></td>
<td align="right"><strong>99%</strong></td>
<td align="right"><strong>0.504 ms</strong></td>
</tr>
<tr>
<td align="left">bloXroute Robinhood API</td>
<td align="right">1</td>
<td align="right">1%</td>
<td align="right">13.769 ms</td>
</tr>
</tbody></table>
<p>BlockRazor won 99 of 100 rounds for a <code>99%</code> win rate; bloXroute won one round for a <code>1%</code> win rate.</p>
<p>BlockRazor's average RPC response was <code>0.504 ms</code>, compared with <code>13.769 ms</code> for bloXroute, making the latter about 27.3 times higher. The onchain receipt still determines the same-nonce winner; API response time alone does not establish which transaction was ultimately included.</p>
<h2><strong>Transaction benchmark 2: Onchain position with distinct nonces</strong></h2>
<p>For the distinct-nonce test, we assigned independent accounts and nonces to the two routes, allowing every transaction to be included. Each round first compared block height; when transactions landed in the same block, it then compared Transaction Index. This is closer to the final onchain position than RPC response time alone.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Result type</strong></th>
<th align="right"><strong>Rounds</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left"><strong>BlockRazor landed in an earlier block</strong></td>
<td align="right"><strong>17</strong></td>
</tr>
<tr>
<td align="left"><strong>Same block, BlockRazor had the earlier Index</strong></td>
<td align="right"><strong>81</strong></td>
</tr>
<tr>
<td align="left">bloXroute landed in an earlier block</td>
<td align="right">1</td>
</tr>
<tr>
<td align="left">Same block, bloXroute had the earlier Index</td>
<td align="right">1</td>
</tr>
</tbody></table>
<p>Across the 81 same-block rounds in which BlockRazor had the earlier Index:</p>
<table>
<thead>
<tr>
<th align="left"><strong>Index difference</strong></th>
<th align="right"><strong>Rounds</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left"><strong>BlockRazor ahead by 1 position</strong></td>
<td align="right"><strong>47</strong></td>
</tr>
<tr>
<td align="left"><strong>BlockRazor ahead by 2 positions</strong></td>
<td align="right"><strong>18</strong></td>
</tr>
<tr>
<td align="left"><strong>BlockRazor ahead by 3 positions</strong></td>
<td align="right"><strong>12</strong></td>
</tr>
<tr>
<td align="left"><strong>BlockRazor ahead by 4 positions</strong></td>
<td align="right"><strong>3</strong></td>
</tr>
<tr>
<td align="left"><strong>BlockRazor ahead by 5 positions</strong></td>
<td align="right"><strong>1</strong></td>
</tr>
</tbody></table>
<p>Final onchain position is evaluated in two stages. An earlier block takes precedence over the transaction's Index within that block; Transaction Index is compared only when both transactions land in the same block. Of the 18 cross-block rounds, BlockRazor landed earlier in 17 and bloXroute landed earlier in one.</p>
<p>Of the remaining 82 same-block rounds, BlockRazor had the earlier Index in 81, a same-block Index win rate of <code>98.78%</code>. Across these 81 winning samples, the most common result was a one-position lead, recorded in 47 rounds. The median Index advantage was one position, both P90 and P95 were three positions, and the average advantage was <code>1.68</code> positions.</p>
<p>Combining block height and same-block Index, BlockRazor achieved the better onchain position in 98 of 100 rounds, compared with two for bloXroute. BlockRazor's average RPC response was <code>0.447 ms</code>, versus <code>12.797 ms</code> for bloXroute; API response speed and final onchain position remain separate measurements.</p>
<h2><strong>How Feed and Transaction Sending form a complete path</strong></h2>
<p>A latency-sensitive trading workflow commonly follows this sequence:</p>
<p><strong>receive a block → decode and update state → evaluate a strategy → construct a transaction → submit → enter Sequencer ordering</strong></p>
<p>This benchmark shows a clear BlockRazor lead on both sides of the workflow. Our Feed delivered all 2,919 matched blocks first, while Transaction Sending achieved a <code>99%</code> same-nonce win rate and a <code>98%</code> distinct-nonce onchain-position win rate. BlockRazor's average RPC response remained below <code>0.6 ms</code> in both submission tests, while bloXroute averaged more than <code>12 ms</code>.</p>
<p>Earlier data and faster submission can preserve more reaction time, but they do not guarantee a fixed onchain position, transaction success, or strategy profitability. Outcomes still depend on transaction construction, network conditions, endpoint routing, competing traffic, and Sequencer ordering.</p>
<h3><strong>Frequently asked questions</strong></h3>
<h4><strong>Why is BlockRazor shown as 0.000 ms in the Feed table?</strong></h4>
<p>This is a relative first-arrival test. The earlier feed for each matched block is assigned <code>0.000 ms</code>; it does not mean that the absolute Sequencer-to-client delivery path took zero time.</p>
<h4><strong>Which products were included in the Feed benchmark?</strong></h4>
<p>The BlockRazor side used the Robinhood Chain Node-required Sequencer Feed included with BlockRazor Package, which connects through a compatible local node. The bloXroute side used the Robinhood Chain Sequencer Feed available in bloXroute Enterprise.</p>
<h4><strong>Was the transaction-submission test one-to-one?</strong></h4>
<p>Yes. Each round in this benchmark had two routes: the BlockRazor Ohio relay and the bloXroute Robinhood API. Both tests contained 100 rounds and did not combine multiple bloXroute endpoints.</p>
<h4><strong>What do the same-nonce and distinct-nonce tests measure?</strong></h4>
<p>The same-nonce test makes several transactions compete for one executable nonce and indicates which route entered ordering first. The distinct-nonce test allows all transactions to be included, then compares their final block heights and Transaction Indexes.</p>
<h2><strong>Test BlockRazor in your environment</strong></h2>
<p>The results point in the same direction on both sides of the workflow: BlockRazor arrived first on all 2,919 Feed samples, won <code>99%</code> of the one-to-one same-nonce races, and achieved the better onchain position in <code>98%</code> of the distinct-nonce rounds. BlockRazor averaged <code>0.504 ms</code> and <code>0.447 ms</code> in RPC response time.</p>
<p>Review our <a href="https://docs.blockrazor.io/streams/node-stream/robinhood-chain/sequencer-feed"><u>Node-required Sequencer Feed documentation</u></a> and <a href="https://docs.blockrazor.io/transaction-submission/transaction-sending/robinhood-chain/eth_sendrawtransaction"><u>Robinhood Chain Transaction Sending documentation</u></a>, then run a simultaneous A/B test against bloXroute from your production region. For teams with stricter latency requirements, we also offer the faster <a href="https://docs.blockrazor.io/streams/node-stream/robinhood-chain/sequencer-feed-ultra"><u>Node-required Sequencer Feed Ultra</u></a>. For integration support, <a href="https://discord.com/invite/qqJuwRb8Nh"><u>contact us</u></a>.</p>
]]></content:encoded></item><item><title><![CDATA[BlockRazor vs bloXroute: A Comparison of Low-Latency Infrastructure Capabilities]]></title><description><![CDATA[Source: Benchmark conclusion: This article compares BlockRazor and bloXroute under consistent test conditions in Virginia, Frankfurt, Dublin, and Tokyo…]]></description><link>https://blockrazor.hashnode.dev/blockrazor-vs-bloxroute-a-comparison-of-low-latency-infrastructure-capabilities</link><guid isPermaLink="true">https://blockrazor.hashnode.dev/blockrazor-vs-bloxroute-a-comparison-of-low-latency-infrastructure-capabilities</guid><dc:creator><![CDATA[luvsreal1994]]></dc:creator><pubDate>Thu, 05 Nov 2026 07:45:52 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/4550534e-dcab-4830-bba8-1afae44e66e7.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Source: <a href="https://blockrazor.io/blog/blockrazor-vs-bloxroute/"><u>https://blockrazor.io/blog/blockrazor-vs-bloxroute/</u></a></p>
<p><strong>Benchmark conclusion:</strong> This article compares BlockRazor and bloXroute under consistent test conditions in Virginia, Frankfurt, Dublin, and Tokyo across Node Stream, Block Stream, mempool transaction monitoring, and public transaction submission. Results are reported using first arrive share, observed transaction coverage, transaction-race win rate, and same-block index position. BlockRazor led every reported regional comparison:</p>
<ul>
<li><strong>Node Stream:</strong> BlockRazor's first arrive share ranged from 53.72% to 75.31%, compared with 17.78% to 45.18% for bloXroute.</li>
<li><strong>Block Stream:</strong> BlockRazor delivered 65.38% to 95.77% of observed blocks first, versus 4.23% to 34.62% for bloXroute.</li>
<li><strong>Mempool transaction monitoring:</strong> BlockRazor's first arrive share ranged from 56.71% to 85.09%, while its observed transaction coverage reached 99.46%–99.76%; bloXroute recorded 14.91%–43.29% first arrive and 69.31%–78.44% observed coverage.</li>
<li><strong>Public transaction submission:</strong> BlockRazor won 747 of 797 races, an overall win rate of 93.73% and more than 90% in every region. Among same-block pairs, it secured the earlier index in 91.62%–96.30% of each region's samples.</li>
</ul>
<h2><strong>Benchmark Scope and Metrics</strong></h2>
<p>This benchmark focuses on low-latency BSC data delivery and public transaction submission. The four test categories use the following decision rules:</p>
<table>
<thead>
<tr>
<th align="left"><strong>Test category</strong></th>
<th align="left"><strong>Decision rule</strong></th>
<th align="left"><strong>Primary outputs</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Node Stream</td>
<td align="left">Identify the source that delivered each block to the test client first</td>
<td align="left">First arrive share and BlockRazor lead-time percentiles for winning samples</td>
</tr>
<tr>
<td align="left">Block Stream</td>
<td align="left">Identify which provider delivered each observed block first</td>
<td align="left">First arrive share and count</td>
</tr>
<tr>
<td align="left">Mempool transaction monitoring</td>
<td align="left">Compare first arrive for transactions seen by both services and coverage of unique transaction hashes</td>
<td align="left">First arrive share and observed coverage</td>
</tr>
<tr>
<td align="left">Public transaction submission</td>
<td align="left">Compare inclusion block first, then transaction index for same-block pairs</td>
<td align="left">Race win rate and same-block index position</td>
</tr>
</tbody></table>
<h2><strong>Node Stream Performance</strong></h2>
<p>Node Stream accelerates the synchronization of the latest blocks and world state to a local node, reducing the window in which that node operates on stale state. For quantitative teams, trading bots, searchers, and node engineering teams that depend on local nodes for strategy decisions, transaction preparation, or on-chain analysis, faster state synchronization provides a more timely foundation for computation, risk control, and execution.</p>
<h3><strong>First arrive share across four regions</strong></h3>
<p>First arrive identifies which source delivered a block to the test client first. It measures arrival frequency: a higher share means that a provider was the earliest source for a larger proportion of observed blocks.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Region</strong></th>
<th align="right"><strong>BlockRazor first arrive</strong></th>
<th align="right"><strong>bloXroute first arrive</strong></th>
<th align="right"><strong>Other P2P</strong></th>
<th align="left"><strong>First arrive leader</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Virginia</td>
<td align="right">75.31%</td>
<td align="right">17.78%</td>
<td align="right">6.91%</td>
<td align="left">BlockRazor</td>
</tr>
<tr>
<td align="left">Frankfurt</td>
<td align="right">74.68%</td>
<td align="right">24.38%</td>
<td align="right">0.94%</td>
<td align="left">BlockRazor</td>
</tr>
<tr>
<td align="left">Dublin</td>
<td align="right">53.72%</td>
<td align="right">45.18%</td>
<td align="right">1.09%</td>
<td align="left">BlockRazor</td>
</tr>
<tr>
<td align="left">Tokyo</td>
<td align="right">68.40%</td>
<td align="right">30.64%</td>
<td align="right">0.96%</td>
<td align="left">BlockRazor</td>
</tr>
</tbody></table>
<p>BlockRazor recorded a higher first arrive share than bloXroute in all four regions. Virginia measured 75.31% versus 17.78%, a difference of 57.53 percentage points. Frankfurt measured 74.68% versus 24.38%, a difference of 50.30 points. Tokyo measured 68.40% versus 30.64%, a difference of 37.76 points. Dublin was the closest at 53.72% versus 45.18%, an 8.54-point difference. Other P2P sources accounted for less than 7% in every region.</p>
<h3><strong>How far ahead was BlockRazor when it won?</strong></h3>
<p>The following table includes only blocks where BlockRazor arrived first and shows the conditional lead-time distribution for those wins. These values measure BlockRazor's winning margin, not end-to-end service latency.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Region</strong></th>
<th align="right"><strong>P50 lead</strong></th>
<th align="right"><strong>P75 lead</strong></th>
<th align="right"><strong>P90 lead</strong></th>
<th align="right"><strong>P95 lead</strong></th>
<th align="right"><strong>P99 lead</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Virginia</td>
<td align="right">3.751 ms</td>
<td align="right">6.513 ms</td>
<td align="right">11.025 ms</td>
<td align="right">14.171 ms</td>
<td align="right">21.697 ms</td>
</tr>
<tr>
<td align="left">Frankfurt</td>
<td align="right">6.295 ms</td>
<td align="right">8.468 ms</td>
<td align="right">11.532 ms</td>
<td align="right">14.611 ms</td>
<td align="right">20.549 ms</td>
</tr>
<tr>
<td align="left">Dublin</td>
<td align="right">4.278 ms</td>
<td align="right">8.375 ms</td>
<td align="right">14.491 ms</td>
<td align="right">19.973 ms</td>
<td align="right">25.798 ms</td>
</tr>
<tr>
<td align="left">Tokyo</td>
<td align="right">3.928 ms</td>
<td align="right">8.610 ms</td>
<td align="right">12.725 ms</td>
<td align="right">16.011 ms</td>
<td align="right">24.512 ms</td>
</tr>
</tbody></table>
<p>Among the samples where BlockRazor arrived first, Frankfurt had the highest P50 lead at 6.295 ms. Dublin showed the largest lead at the higher percentiles, with P90, P95, and P99 values of 14.491 ms, 19.973 ms, and 25.798 ms. Tokyo recorded a P50 lead of 3.928 ms and a P99 lead of 24.512 ms. In other words, BlockRazor maintained millisecond-level median and higher-percentile advantages within the samples it won.</p>
<h2><strong>Block Stream Monitoring</strong></h2>
<p>Block Stream provides low-latency delivery of the latest blocks and their confirmed transactions, allowing monitoring and strategy systems to update confirmed state sooner. It can support monitoring for target addresses, popular contracts, and anomalous transactions, while also supplying block headers, transaction lists, and subsequent block-producer information for block-level analysis. Combined with mempool and transaction-submission services, it forms a monitoring, decision, and execution workflow. This section compares which provider delivered each observed block first.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Region</strong></th>
<th align="right"><strong>BlockRazor first arrive</strong></th>
<th align="right"><strong>bloXroute first arrive</strong></th>
<th align="right"><strong>BlockRazor wins</strong></th>
<th align="right"><strong>bloXroute wins</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Virginia</td>
<td align="right">95.77%</td>
<td align="right">4.23%</td>
<td align="right">45,916</td>
<td align="right">2,028</td>
</tr>
<tr>
<td align="left">Frankfurt</td>
<td align="right">77.07%</td>
<td align="right">22.93%</td>
<td align="right">36,888</td>
<td align="right">10,974</td>
</tr>
<tr>
<td align="left">Dublin</td>
<td align="right">65.38%</td>
<td align="right">34.62%</td>
<td align="right">31,371</td>
<td align="right">16,610</td>
</tr>
<tr>
<td align="left">Tokyo</td>
<td align="right">80.63%</td>
<td align="right">19.37%</td>
<td align="right">38,434</td>
<td align="right">9,234</td>
</tr>
</tbody></table>
<p>Virginia recorded the highest BlockRazor first arrive share at 95.77%, versus 4.23% for bloXroute. Tokyo measured 80.63% versus 19.37%, a difference of 61.26 percentage points and 38,434 versus 9,234 first arrive blocks. Frankfurt measured 77.07% versus 22.93%, while Dublin measured 65.38% versus 34.62%. BlockRazor's first arrive share ranged from 65.38% to 95.77% across the four regions, although the size of the lead varied substantially by region.</p>
<h2><strong>Mempool Transaction Monitoring</strong></h2>
<p>Mempool transaction monitoring provides low-latency access to publicly propagated pending-transaction signals before on-chain inclusion, allowing strategies to begin evaluation, parameter calculation, and risk control sooner. It can support pending-transaction monitoring, Smart Money tracking, backrunning, copy trading, and sniping. This section evaluates two dimensions: which provider arrived first for transactions observed by both services, and what share of all unique transaction hashes each provider observed.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Region</strong></th>
<th align="right"><strong>BlockRazor first arrive</strong></th>
<th align="right"><strong>bloXroute first arrive</strong></th>
<th align="right"><strong>BlockRazor observed share</strong></th>
<th align="right"><strong>bloXroute observed share</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Virginia</td>
<td align="right">85.09%</td>
<td align="right">14.91%</td>
<td align="right">99.72%</td>
<td align="right">77.86%</td>
</tr>
<tr>
<td align="left">Frankfurt</td>
<td align="right">61.10%</td>
<td align="right">38.90%</td>
<td align="right">99.68%</td>
<td align="right">76.73%</td>
</tr>
<tr>
<td align="left">Dublin</td>
<td align="right">56.71%</td>
<td align="right">43.29%</td>
<td align="right">99.76%</td>
<td align="right">69.31%</td>
</tr>
<tr>
<td align="left">Tokyo</td>
<td align="right">76.92%</td>
<td align="right">23.08%</td>
<td align="right">99.46%</td>
<td align="right">78.44%</td>
</tr>
</tbody></table>
<p>For first arrive, BlockRazor measured 85.09% in Virginia, 76.92% in Tokyo, 61.10% in Frankfurt, and 56.71% in Dublin, leading bloXroute in all four regions. For observed share, BlockRazor ranged from 99.46% to 99.76% across the four regions, compared with 69.31% to 78.44% for bloXroute. Dublin had the largest observed-share gap at 30.45 percentage points. Here, observed share is the number of unique transaction hashes seen by a provider divided by the union of unique hashes seen by both providers during the test; it does not measure on-chain inclusion.</p>
<h2><strong>Public Transaction Submission</strong></h2>
<p>Public transaction submission sends signed transactions into public propagation and the on-chain execution path through a low-latency route. It can serve as a fast submission entry point without requiring an additional tip in the transaction. This approach suits teams prioritizing inclusion speed without making private propagation or MEV protection the primary requirement. The benchmark used paired submissions: the earlier inclusion block determined the winner, and if both transactions landed in the same block, the lower transaction index determined the winner.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Region</strong></th>
<th align="right"><strong>Valid pairs</strong></th>
<th align="right"><strong>BlockRazor wins</strong></th>
<th align="right"><strong>bloXroute wins</strong></th>
<th align="right"><strong>BlockRazor win rate</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Virginia</td>
<td align="right">199</td>
<td align="right">192</td>
<td align="right">7</td>
<td align="right">96.48%</td>
</tr>
<tr>
<td align="left">Frankfurt</td>
<td align="right">200</td>
<td align="right">182</td>
<td align="right">18</td>
<td align="right">91.00%</td>
</tr>
<tr>
<td align="left">Dublin</td>
<td align="right">200</td>
<td align="right">185</td>
<td align="right">15</td>
<td align="right">92.50%</td>
</tr>
<tr>
<td align="left">Tokyo</td>
<td align="right">198</td>
<td align="right">188</td>
<td align="right">10</td>
<td align="right">94.95%</td>
</tr>
</tbody></table>
<p>Across 797 valid public-transaction races, BlockRazor won 747, for an overall win rate of 93.73%. In Virginia, it won 192 of 199 pairs, or 96.48%. In Tokyo, it won 188 of 198 pairs, or 94.95%. It won 185 of 200 pairs in Dublin, or 92.50%, and 182 of 200 pairs in Frankfurt, or 91.00%. BlockRazor's win rate exceeded 90% in all four regions.</p>
<h3><strong>Same-block index comparison for public transactions</strong></h3>
<p>When both transactions landed in the same block, the lower index occupied the earlier position. The following table includes only same-block pairs. Average and maximum index advantages are calculated separately from the pairs won by each provider.</p>
<table>
<thead>
<tr>
<th align="left"><strong>Region</strong></th>
<th align="right"><strong>Same-block pairs</strong></th>
<th align="right"><strong>BlockRazor earlier index</strong></th>
<th align="right"><strong>bloXroute earlier index</strong></th>
<th align="right"><strong>BlockRazor average lead (max)</strong></th>
<th align="right"><strong>bloXroute average lead (max)</strong></th>
</tr>
</thead>
<tbody><tr>
<td align="left">Virginia</td>
<td align="right">189</td>
<td align="right">182</td>
<td align="right">7</td>
<td align="right">4.10 positions (81)</td>
<td align="right">3.14 positions (8)</td>
</tr>
<tr>
<td align="left">Frankfurt</td>
<td align="right">191</td>
<td align="right">175</td>
<td align="right">16</td>
<td align="right">2.54 positions (33)</td>
<td align="right">2.38 positions (15)</td>
</tr>
<tr>
<td align="left">Dublin</td>
<td align="right">188</td>
<td align="right">173</td>
<td align="right">15</td>
<td align="right">3.71 positions (73)</td>
<td align="right">2.67 positions (4)</td>
</tr>
<tr>
<td align="left">Tokyo</td>
<td align="right">188</td>
<td align="right">178</td>
<td align="right">10</td>
<td align="right">3.47 positions (81)</td>
<td align="right">4.90 positions (15)</td>
</tr>
</tbody></table>
<p>Many public-transaction comparisons were decided by ordering inside the same block. BlockRazor secured the earlier index in 182, 175, 173, and 178 same-block pairs in Virginia, Frankfurt, Dublin, and Tokyo, respectively, representing 96.30%, 91.62%, 92.02%, and 94.68% of each region's same-block sample.</p>
<h2><strong>Final Conclusion</strong></h2>
<p>Under the test conditions and decision rules used in this article, BlockRazor led the Node Stream, Block Stream, and mempool transaction first arrive comparisons in Virginia, Frankfurt, Dublin, and Tokyo; its mempool observed share remained between 99.46% and 99.76%, and its public transaction-race win rate exceeded 90% in every region. These results show a consistent BlockRazor advantage across the BSC low-latency data-delivery and public transaction-submission metrics covered by this benchmark, supporting its evaluation as an alternative to bloXroute; the conclusion remains limited to the stated test periods, regions, network conditions, and measurement rules.</p>
<h2><strong>Benchmark Data and Measurement Notes</strong></h2>
<ul>
<li>This article uses like-for-like BlockRazor and bloXroute tests from Virginia, Frankfurt, Dublin, and Tokyo. Each regional benchmark ran for six hours between September 23 and 25, 2026.</li>
<li>Node Stream first arrive share assigns each block to the source that reached the test client first, with other P2P sources counted separately. Lead-time percentiles include only samples where BlockRazor arrived first and do not represent end-to-end service latency.</li>
<li>Block Stream uses the first provider to deliver each observed block as the decision rule. Virginia, Frankfurt, Dublin, and Tokyo contained 47,944, 47,862, 47,981, and 47,668 first arrive decisions, respectively.</li>
<li>Mempool transaction first arrive compares only transactions observed by both services. Observed share uses the union of unique transaction hashes seen by both providers during the test as its denominator, so it is not a transaction-inclusion rate.</li>
<li>The public transaction test used paired submissions. The earlier inclusion block determined the winner; if both transactions entered the same block, the lower transaction index won. The test contained 797 valid pairs. Same-block average and maximum index leads are calculated separately from the samples won by each provider.</li>
<li>All results are specific to the test periods, regions, network conditions, and decision rules described above. They should not be treated as fixed performance differences across every deployment environment.</li>
</ul>
]]></content:encoded></item><item><title><![CDATA[Robinhood Chain Transaction Submission Benchmark: Four-Way Race]]></title><description><![CDATA[October 26, 2026 Ohio-2b benchmark: BlockRazor won 56/100 same-nonce races and took the earliest onchain position in 61/100 distinct-nonce rounds. Source:]]></description><link>https://blockrazor.hashnode.dev/robinhood-chain-transaction-submission-benchmark-four-way-race</link><guid isPermaLink="true">https://blockrazor.hashnode.dev/robinhood-chain-transaction-submission-benchmark-four-way-race</guid><dc:creator><![CDATA[luvsreal1994]]></dc:creator><pubDate>Thu, 05 Nov 2026 07:36:13 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/8436a1a1-4f65-4c88-b6dc-6e1d7f1c9414.webp" length="0" type="image/jpeg"/><content:encoded><![CDATA[<blockquote>
<p>October 26, 2026 Ohio-2b benchmark: BlockRazor won 56/100 same-nonce races and took the earliest onchain position in 61/100 distinct-nonce rounds.</p>
</blockquote>
<p>Source: <a href="https://blockrazor.io/blog/robinhood-transaction-submission-four-way-benchmark/">https://blockrazor.io/blog/robinhood-transaction-submission-four-way-benchmark/</a></p>
<p>Updated: 2026-10-27</p>
<p>On October 26, 2026, we ran two 100-round transaction-submission races on Robinhood Mainnet from Ohio-2b. The four paths under test were BlockRazor, bloXroute, Eira Nodes, and Node1.</p>
<p>BlockRazor won 56 of 100 rounds in the four-way same-nonce race. In the distinct-nonce onchain-position test, BlockRazor took the earliest position among all four transactions in 61 of 100 rounds. In pairwise comparisons derived from the distinct-nonce test, BlockRazor finished ahead of bloXroute in 100/100 comparable rounds, ahead of Eira Nodes in 71/99, and ahead of Node1 in 82/100.</p>
<h2>Key results</h2>
<p>Same-nonce four-way race: BlockRazor won 56/100 rounds, the highest share among the four paths.</p>
<p>Distinct-nonce full-field ordering: BlockRazor took the earliest onchain position in 61/100 rounds.</p>
<p>BlockRazor vs bloXroute: BlockRazor finished ahead in 100/100 comparable samples.</p>
<p>BlockRazor vs Eira Nodes: BlockRazor finished ahead in 71/99 comparable samples.</p>
<p>BlockRazor vs Node1: BlockRazor finished ahead in 82/100 comparable samples.</p>
<h2>Benchmark setup: four paths from the same Ohio-2b test machine</h2>
<p>Both tests ran on Robinhood Mainnet, Chain ID 4663, from the same Ohio-2b test machine. Each test contained 100 rounds with a five-second interval between rounds.</p>
<p>Service Endpoint tested</p>
<p>BlockRazor <a href="https://us.robinhood.blockrazor.io">https://us.robinhood.blockrazor.io</a></p>
<p>bloXroute <a href="https://api.blxrbdn.com">https://api.blxrbdn.com</a></p>
<p>Eira Nodes <a href="https://send.eiranodes.dev">https://send.eiranodes.dev</a></p>
<p>Node1 <a href="https://robinhood-ohio-2b.node1.me">https://robinhood-ohio-2b.node1.me</a></p>
<p>The same test process triggered all four requests in each round. The raw logs show a median launch spread of approximately 90 μs and a P90 spread of 163 μs in the same-nonce test. In the distinct-nonce test, the corresponding values were approximately 89 μs and 140 μs. The path launched first was also distributed across all four services rather than being fixed to BlockRazor.</p>
<p>Transaction type, fee conditions, and execution complexity were matched within each round. Final results were determined from onchain receipts. A transaction in an earlier block ranked first; when transactions landed in the same block, the lower transactionIndex ranked first.</p>
<h2>Result 1: BlockRazor won 56% of the four-way same-nonce races</h2>
<p>The same-nonce test models multiple submission paths competing for the same executable opportunity. In each round, the four transactions used the same sender and nonce. Because that nonce can be consumed only once, at most one of the competing transactions can be included. The transaction that lands identifies the submission path that first entered valid Sequencer ordering for that round.</p>
<p>To identify the four paths onchain, the transactions used adjacent gas limits from 30000 to 30003. Fee parameters and execution content remained matched, and actual gas usage was below all four limits.</p>
<img src="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/53cefdb2-22e1-4401-a8b2-f7c674e40a19.png" alt="" style="display:block;margin:0 auto" />

<p>The 56% figure is a four-way win share, not a 56% pairwise win rate against each provider. It answers a specific question: when all four paths compete for one executable nonce at the same time, which path most often enters valid ordering first?</p>
<h2>Result 2: BlockRazor took the earliest onchain position in 61% of rounds</h2>
<p>A same-nonce race leaves only one transaction onchain, so it cannot show where the other three transactions would have landed. The distinct-nonce test used independent funded accounts and nonces for the four paths, allowing all four transactions to execute. Its purpose is to compare the final onchain positions obtained by each route when every transaction can land.</p>
<p>Each round was classified first by block height. If multiple transactions landed in the same block, the lower transactionIndex was ranked earlier. This produced one full-field winner for each round.</p>
<img src="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/1c9a6bfe-38c3-4442-bbc1-9e585cc4f59e.png" alt="" style="display:block;margin:0 auto" />

<p>To show the concrete ordering gap within the same block, we also calculated competitor transactionIndex − BlockRazor transactionIndex. A positive value means BlockRazor received the lower index and earlier onchain position; a negative value means the competitor was earlier. The mean and percentiles below include only pairs that landed in the same block. Rounds in which BlockRazor landed in an earlier block are reported separately and are not mixed into the index-difference distribution.</p>
<img src="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/f5170961-268b-4edb-ad65-4d7ec90545ff.png" alt="" style="display:block;margin:0 auto" />

<p>Against bloXroute, BlockRazor landed in an earlier block in nine rounds and received the lower index in all 91 remaining same-block samples, with a median lead of three positions. The Eira Nodes and Node1 same-block samples include rounds won by either path, so their rows use the full signed difference distribution; the mean and P50 nevertheless remained positive in both comparisons.</p>
<h2>Head-to-head: BlockRazor’s onchain position against each path</h2>
<p>The distinct-nonce results also support pairwise comparisons between BlockRazor and each other submission path. BlockRazor was classified as ahead when it landed in an earlier block or, within the same block, received a lower transactionIndex.</p>
<img src="https://cdn.hashnode.com/uploads/covers/6ae33f45a689abae0d3f2bea/8b2a6a7e-487c-4078-b0ac-4e8667d09f4d.png" alt="" style="display:block;margin:0 auto" />

<h3>BlockRazor vs bloXroute: ahead in 100/100 onchain comparisons</h3>
<p>BlockRazor obtained the earlier onchain position in all 100 comparable rounds: it landed in an earlier block in nine rounds and received a lower <code>transactionIndex</code> in all 91 same-block rounds. The exact index differences are reported in the Result 2 table above.</p>
<h3>BlockRazor vs Eira Nodes: ahead in 71/99 comparisons</h3>
<p>BlockRazor and Eira Nodes had 99 comparable rounds. BlockRazor finished ahead in 71, while Eira Nodes finished ahead in 28. BlockRazor landed in an earlier block once; the index distribution for the other 98 rounds appears in Result 2.</p>
<h3>BlockRazor vs Node1: ahead in 82/100 comparisons All 100</h3>
<p>BlockRazor and Node1 rounds were comparable. BlockRazor finished ahead in 82 and Node1 in 18. BlockRazor landed in an earlier block once; the index distribution for the other 99 rounds appears in Result 2.</p>
<h2>Why the submission path affects ordering on Robinhood Chain</h2>
<p><a href="https://docs.robinhood.com/chain/#predictable-transaction-ordering">Robinhood Chain documentation</a> states that the network uses first-come, first-served sequencing. Ordering is determined by arrival time at the Sequencer, and a later transaction cannot simply pay a higher fee to bypass an earlier one.</p>
<p>For latency-sensitive systems, the submission path can therefore affect two directly observable outcomes: whether a transaction enters an earlier block and, when competing transactions enter the same block, whether it receives a lower Transaction Index. That is why this benchmark uses both test designs. Same-nonce races measure direct competition for one executable opportunity; distinct-nonce races verify the final positions when every transaction can land.</p>
<h2>What the results mean for trading systems</h2>
<p>For sniping, arbitrage, liquidations, and other state-dependent strategies, reaching the Sequencer earlier can improve the probability that the intended execution conditions still exist. For searchers and quantitative systems, a lower-latency submission path preserves more of the reaction window between receiving a signal, completing computation, and reaching ordering.</p>
<p>For wallets, DEXs, and orderflow applications, an optimized submission path can improve the probability of an earlier block or better index without changing the end user’s workflow.</p>
<p>BlockRazor optimizes the path used to deliver a signed transaction to the Robinhood Chain Sequencer. A lower-latency path can improve ordering probability, but it does not guarantee a specific block, a fixed Transaction Index, transaction success, or strategy profitability. Final outcomes still depend on transaction validity, network conditions, competing flow, and Sequencer ordering.</p>
<h2>Sequencer Feed plus Transaction Sending: from signal to submission</h2>
<p>The reaction path for a latency-sensitive trading system typically looks like this:</p>
<p><strong>Receive block → update state → evaluate strategy → build transaction → submit transaction → enter Sequencer ordering</strong></p>
<p>BlockRazor Robinhood Chain Sequencer<a href="https://docs.blockrazor.io/streams/node-stream/robinhood-chain/sequencer-feed-ultra">BlockRazor Robinhood Chain Sequencer Feed</a> optimizes the receive side by helping systems obtain new blocks earlier. <a href="https://docs.blockrazor.io/transaction-submission/transaction-sending/robinhood-chain/eth_sendrawtransaction">Transaction Sending</a> optimizes the send side by routing signed transactions toward Robinhood Chain through a low-latency path. The services can be used independently or combined into an end-to-end path from onchain signal to transaction submission.</p>
<h2>Conclusion: run the same race from your production environment</h2>
<p>In the October 26, 2026 Ohio-2b benchmark, BlockRazor won 56/100 rounds in the four-way same-nonce race and took the earliest full-field position in 61/100 distinct-nonce rounds. Pairwise onchain comparisons placed BlockRazor ahead of bloXroute, Eira Nodes, and Node1 in 100/100, 71/99, and 82/100 comparable rounds respectively.</p>
<p>Teams whose execution depends on ordering can run the same A/B test from their production region: trigger matched transactions across multiple paths, record receipts, block heights, and transactionIndex, and repeat the measurement across different time windows.</p>
<p>BlockRazor Robinhood Chain Transaction Sending supports the standard eth_sendRawTransaction method. Read the <a href="https://docs.blockrazor.io/transaction-submission/transaction-sending/robinhood-chain/eth_sendrawtransaction">integration documentation</a>, or contact BlockRazor on <a href="https://discord.com/invite/qqJuwRb8Nh">Discord</a> to benchmark the service from your own trading environment.</p>
<h2>Frequently asked questions</h2>
<h3>What do the same-nonce and distinct-nonce tests measure?</h3>
<p>The same-nonce test makes four transactions compete for one executable nonce, so only one can land and identify the path that entered valid ordering first. The distinct-nonce test allows all four transactions to execute, then compares their block heights and, within the same block, their transactionIndex values.</p>
<h3>How was the earlier onchain position determined?</h3>
<p>The benchmark compared block height first, with a transaction in an earlier block ranked ahead. When transactions landed in the same block, the lower transactionIndex ranked earlier. Cross-block outcomes were kept separate from the mean and percentile calculations for same-block index differences.</p>
<h3>Why were only 99 BlockRazor and Eira Nodes rounds comparable?</h3>
<p>The distinct-nonce test ran for 100 rounds, but one Eira Nodes transaction did not obtain an onchain receipt. That round could not support a pairwise onchain-position comparison, so the BlockRazor versus Eira Nodes head-to-head result uses the remaining 99 comparable samples.</p>
<h3>Do these results guarantee the same performance in every region and time window?</h3>
<p>No. The results come from the listed endpoints and an Ohio-2b test machine on October 26, 2026. Network routing, endpoint deployment, load, and competing traffic can change the outcome. Teams should repeat the same matched-transaction test from their own production region.</p>
]]></content:encoded></item></channel></rss>