> 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/solana/geyser-stream.md). # Geyser Stream ### **什麼是Geyser Stream** Geyser 是 Solana 驗證者的插件機制，可將鏈上的 `account`、`slot`、`block` 和 `transaction` 等數據實時輸出到外部系統。Geyser Stream 是 BlockRazor 基於 Yellowstone gRPC 推出的 Solana 高性能數據流服務，支持客戶端通過 gRPC 以極低延遲訂閱結構化的實時鏈上數據。 ### **Geyser Stream的應用場景** * **交易分析：** 監聽指定賬戶的交易，用於跟單聰明錢賬戶交易，或捕捉 pump.fun 新幣等早期信號 * **賬戶分析：** 監聽指定賬戶餘額變化，用於跟蹤 Raydium、Orca、Jupiter 等 DEX 池子賬戶狀態，進一步計算代幣對價格 * **區塊與槽位分析：** 監聽區塊和槽位更新，用於觀察網絡共識進度與節點健康狀態 ### **Geyser Stream的關鍵特性** * **高性能：** 基於高性能服務器和低延遲鏈路，實時向客戶端推送 gRPC 數據流 * **數據完整性：** 支持最近 500 個 slot（約 200 秒）的交易重放，斷連後可快速補齊數據 * **高穩定性：** 服務採用多雲多實例部署，支持無縫故障轉移，保障長時間穩定運行 ### 常见问题
Geyser Stream和Shred Stream有什麼區別 兩者的核心區別在於**數據層級**和**使用門檻**。Shred Stream 傳輸的是更底層的原始 `shred`，鏈路更短，延遲更低，適合極度追求時效的 Bots、RPC 和 Validators，但接入方需要自己做重組和解析；Geyser Stream 傳輸的是結構化的 `account`、`slot`、`block` 和 `transaction` 數據，客戶端可直接通過 gRPC 訂閱，接入更簡單，也更適合賬戶監聽、交易分析和穩定生產環境。若你要的是**更早的交易信號**，優先選 [Shred Stream](/tc/streams/block-stream/solana/shred-stream.md)；若你要的是**更完整、易消費的實時鏈上數據**，優先選 [Geyser Stream](/tc/streams/block-stream/solana/geyser-stream.md)。
### 快速开始 {% stepper %} {% step %} **采购Geyser Stream** 前往[订阅](https://blockrazor.io/#/pricing)页面采购Geyser Stream {% endstep %} {% step %} **获取Auth** 详见 [Authentication](/tc/get-started/authentication.md) {% endstep %} {% step %} **集成Geyser Stream** 多語言客戶端集成詳見： * [CLI](/tc/streams/block-stream/solana/geyser-stream/cli.md) * [Go](/tc/streams/block-stream/solana/geyser-stream/go.md) * [Rust](/tc/streams/block-stream/solana/geyser-stream/rust.md) * [JS](/tc/streams/block-stream/solana/geyser-stream/js.md) {% endstep %} {% endstepper %} ### 端點
地區端點
東京geyserstream-tokyo.blockrazor.xyz:443
### 價格 {% hint style="info" %} Geyser Stream按週期（單位：月）流量收費，價格在新採購、續費、新增流量等場景下一致 {% endhint %} | 週期流量 | 折扣 | 折後價 / 週期 | | ------- | ---- | -------- | | 5 TiB | 100% | $250 | | 10 TiB | 100% | $500 | | 50 TiB | 100% | $2500 | | 100 TiB | 95% | $4750 | | 150 TiB | 90% | $6750 | | 200 TiB | 85% | $8500 | | 250 TiB | 80% | $10000 | #### 採購說明
新採購續費增加週期流量
場景首次採購或流量過期後再次採購Geyser Stream在Geyser Stream流量週期內續費Geyser Stream週期流量提前消耗殆盡，需補充流量
結果根據採購時長生成週期流量。延遲流量週期不延長有效期，只增加週期內的流量
例子新採購5 TiB 1個週期，則可用流量為：
- 起始週期：5 TiB		採購5 TiB 1個週期，在起始週期內續費1個週期，則可用流量為：
- 起始週期：5 TiB
- 第2週期：10 TiB		採購5 TiB 1個週期，同時續費10 Tib 1個週期，起始週期內發現流量消耗殆盡，選擇在起始週期新增流量 5 Tib
- 起始週期：5 Tib + 5 Tib
- 第2週期：10 Tib
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.blockrazor.io/tc/streams/block-stream/solana/geyser-stream.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.