On November 10, 2026, Jinse Finance reported that a CryptoQuant report found several Bitcoin indicators had turned bearish, with the market at a threshold between building a base and a deeper pullback. The figures below are those in that report as carried by Jinse. They describe conditions relative to the November 10, 2026 report, not a later market update.
Reported price change and indicator readings
CryptoQuant’s report said Bitcoin had fallen 9% over the prior 30 days and was 15% below the September high. Its bull-market score index had fallen from 90 to 20, which the report placed in an extremely bearish range.
The same summary said 30-day apparent demand had contracted by 284,000 BTC, USDT market capitalization had declined by $6.6 billion over 60 days, and traders’ unrealized return rate had fallen to −6%.
Levels cited in the report
The report said Bitcoin had broken below the 365-day moving average at $76,400 and identified $73,200 as key support.
What CryptoQuant expected, and on what condition
As summarized by Jinse Finance, the report expected Bitcoin to build a base between $70,000 and $76,000 over the following several weeks. It said a break of key support would open a deeper pullback. That range and that break condition are the report’s expectations. They are not a conclusion of this site, and the source does not add probabilities, exact calendar dates for the September high or the 30- and 60-day windows, or further price targets.
Boundary of the reading
The bearish framing rests on the reported mix of a much lower bull-market score, weaker apparent demand, a smaller USDT market cap, a −6% unrealized return rate for traders, and a close below the cited 365-day average. On the report’s own terms, holding the $73,200 support would be consistent with its several-week $70,000–$76,000 base, while losing that support is the condition it tied to a deeper decline. This rewrite does not add trade instructions or any outlook beyond those statements.
Jinse Finance published the item on November 10, 2026, at 22:38 (UTC+8). This English article is a later restatement of that report and should not be read as describing a new or same-day development.
