bitunix

Long-Term Holder SOPR (LTH-SOPR)

رینج
  • 1M1M
  • 3M3M
  • 6M6M
  • 1Y1Y
  • ALLALL
اسکیل
  • لینیئرلینیئر
  • لاگلاگ
تازہ ترین
1D تبدیلی
7D تبدیلی
30D تبدیلی
4Y پرسنٹائل
تاریخی بلند ترین سطح
1Y حد
ڈیٹا لوڈ ہو رہا ہے…

اس پیمانے کے بارے میں

یہ کیا ناپتا ہے

Long-Term Holder SOPR (LTH-SOPR) compares the aggregate USD value at spending of outputs held for at least 155 days with their USD value at creation. It is a unitless multiple of the acquisition value of the older coins spent that day, not of all long-term holdings.

اسے کیسے پڑھیں

Large multiples mean the older coins moving that day carry substantial gains; a reading below 1 means even this spent older cohort realizes an aggregate loss. The series reached about 13.45 on April 14, 2021 and about 0.351 on November 26, 2022. Because the range is wide, the default logarithmic scale makes proportional differences easier to see.

A few very old, low-cost outputs can produce a huge reading without large transfer volume. Conversely, old coins created at high prices can realize losses while much of the long-term supply remains profitable. Check spent volume alongside the 7-day average, and allow for self-transfers and the limited price information in Bitcoin's earliest years.

فریکوئنسی
روزانہ (UTC 00:00)
اثاثہ
BTC
قسم
واحد قدر
ڈیٹا کا آغاز
2009-01-12
تازہ ترین ڈیٹا
2026-11-02

اکثر پوچھے گئے سوالات

Why can LTH-SOPR be far higher than STH-SOPR?

Older coins may have been created when BTC was much cheaper, so their spending value can be many times their acquisition value. The historical maximum here is 397.7 on June 13, 2011, an early-market extreme that is not a modern-cycle threshold.

Does high LTH-SOPR mean many long-term holders are moving coins?

Not necessarily. It measures a value multiple, not a coin count or number of holders. A small transfer with a very low cost basis can raise the ratio sharply.

Why does the LTH-SOPR chart begin later than other SOPR charts?

Outputs must first age at least 155 days and then be spent to qualify. Although the configured history begins in January 2009, the first non-null observation in this series is October 12, 2009.

تلاش کریں
مزید