---
title: BlockRazor Base Infrastructure
description: Base FlashBlock, completed block streams, and regional transaction-submission infrastructure.
canonical: https://blockrazor.io/chains/base/
language: en
last-updated: 2026-10-23
---

# BlockRazor Base Infrastructure

BlockRazor provides pre-confirmation signals, completed block data, and regional transaction paths for latency-sensitive applications on Base.

## Services

- **FlashBlock Stream:** receive sub-block updates over gRPC or WebSocket before a completed Base block is formed.
- **Block Stream:** continuously receive completed Base blocks through regional gRPC endpoints.
- **Transaction Sending:** submit signed Base transactions through regional HTTPS endpoints toward the Base Sequencer.

FlashBlock is intended for earlier awareness, while Block Stream provides completed block data. Transaction Sending completes the path from signal to execution. Current regions, interfaces, and access requirements are maintained in the official documentation.

## Frequently asked questions

### How can I access faster FlashBlock data on Base?

Subscribe to BlockRazor FlashBlock Stream over gRPC or WebSocket from the nearest supported region. FlashBlock is a sub-block update typically pushed about every 200ms before the completed Base block, so applications can react earlier than if they wait for the roughly two-second final block.

### Which Base services fit a high-frequency trading system?

Use FlashBlock Stream for pre-confirmation signals, Block Stream for completed blocks and confirmed transactions, and regional Transaction Sending for eth_sendRawTransaction. Measure the full signal-to-submission path from the same production region because the fastest component alone does not determine end-to-end latency.

### How can I help a transaction reach the Base Sequencer as quickly as possible?

Send the signed transaction through the nearest BlockRazor Base endpoint using gRPC or HTTPS and keep the client connection warm where possible. Test regional latency, retries, and tail behavior with the production workload; lower transport latency can improve arrival time but cannot guarantee ordering or inclusion.

### When should I use Block Stream instead of FlashBlock Stream?

Use Block Stream when the application needs completed blocks and confirmed transactions. Use FlashBlock Stream when earlier pre-confirmation awareness is more important than waiting for the final block.

### Which protocols does BlockRazor support on Base?

FlashBlock Stream supports gRPC and WebSocket. Block Stream uses gRPC. Transaction Sending supports gRPC and HTTPS for eth_sendRawTransaction.

### Where are the Base endpoints located?

Current documentation lists Frankfurt, Tokyo, and Virginia. Applications should select the nearest regional endpoint and validate latency with their own production workload.

## Resources

- Base page: https://blockrazor.io/chains/base/
- Website resource index: https://blockrazor.io/llms.txt
- Traditional Chinese resource index: https://blockrazor.io/zh/llms.txt
- Documentation index: https://docs.blockrazor.io/llms.txt
- FlashBlock documentation: https://docs.blockrazor.io/streams/block-stream/base/get-flashblockstream.md
- Base Transaction Sending: https://docs.blockrazor.io/transaction-submission/transaction-sending/base.md