> For the complete documentation index, see [llms.txt](https://glossary.bshare.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glossary.bshare.io/metrics/jia-ge-fen-bu-price-distribution/shu-chu-jia-ge-fen-bu-spent-output-price-distribution.md).

# 輸出價格分布｜Spent Output Price Distribution ）

## 指標概念

輸出價格分佈 （SOPD） 顯示了 UTXO 在給定日期花費的價格（即每個條形圖顯示在該指定價格桶內移動的比特幣交易量）。 x 軸上指定的價格是指該桶的下限。 該指標有兩種基於 x 軸分區的變體：&#x20;

1. ATH 分區（通過將 0 和當前 ATH 之間的範圍劃分為 100 個等距分區來定義價格條）&#x20;
2. 百分比分區（價格條定義為採用當天的收盤價並在收盤價上方和下方分別創建 50 個等間距的桶，步長為 +／- 2%）

![圖片來源：glassnode](https://lh5.googleusercontent.com/nHxNbbL8cCz968o5LPMDnXi31KI31BCbeE6RO-8Oc0EToakRuG4F9Y1zdmtVtiw-syJp2XUm2Kq72B_TkUIklT9HZUM6KBtRg0_TBmUNFzRO0E0j51h3rGvLML3GKU8IA3PY7UE2)

## **指標如何衡量、計算？**

SOPD 價格條顯示了將所有創建時價格落入給定價位帶的 UTXO 相加而成的價值。


---

# 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://glossary.bshare.io/metrics/jia-ge-fen-bu-price-distribution/shu-chu-jia-ge-fen-bu-spent-output-price-distribution.md?ask=<question>&goal=<endgoal>
```

`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.
