> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/tc/streams/block-stream.md). # 實時區塊數據流 Block Stream 服務 比較 BlockRazor 在各鏈提供的實時區塊數據流 Block Stream，了解區塊數據類型、適用場景和接入路徑。
鏈服務描述
SolanaShred Stream低延遲傳輸shred
SolanaGeyser Stream實時傳輸Solana鏈上數據，包含account, slot, block和transaction等
BSCNewBlocks低延遲訂閱BSC區塊數據
EthereumNewBlocks低延遲訂閱Ethereum區塊數據
BaseGet BlockStream低延遲獲取Base Block數據
BaseGet FlashBlockStream低延遲獲取Base FlashBlock數據
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.blockrazor.io/tc/streams/block-stream.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.