Bitcoin’s Largest Holders Move Markets.
We Make Their Moves Visible.

An exchange reserve sent out
almost everything.

An exchange-associated reserve sent no BTC in October 2025. In November, it sent roughly 32,909 BTC and finished with only 2,368 BTC.

A reserve holds funds apart from day-to-day payments. When most of those funds leave, the operating picture changes.

Start with the balance, then ask where the money went. That separates a large movement from a useful explanation.

An exchange can move reserves to fund customer withdrawals, meet jurisdictional requirements, or change its security arrangements. Its receiving wallet could belong to the same operator.

For your own wallets, payment instructions and wallet records establish the purpose. Public history supplies the amounts, timing, and relationships to compare against them.

A treasury held its January funds
through September.

A treasury-associated wallet received about 26,916 BTC in January 2026. At the end of September, it still held that amount, with no recorded outgoing BTC in its history.

One incoming transfer can be temporary. A history with no outgoing Bitcoin supports a much stronger observation: the funds remained in place.

Watch both directions. A reserve released most of its funds. A treasury received funds and kept them for months.

For a treasury team, this answers a different question from “did money arrive?” It shows whether the selected wallet subsequently sent that money elsewhere.

The published January, April, and September balances are separate observations. The zero-outgoing history is what supports retention between them.

A second reserve emptied
when Bitcoin’s daily reference price was $62,752.

Another exchange-associated reserve went from 26,182 BTC to almost zero during August 2026. Its three largest August transfers happened within six minutes, with a $62,752 daily market reference.

The first reserve sent funds around $90–95k. This reserve became active around $63k. Price Layers show the market context of each change.

The largest movement in this burst was roughly 19,632 BTC. Seeing the individual times reveals a short operational episode inside the monthly total.

A market analyst can compare when different reserves become active. An operations team can match the same episode to its planned movements.

Both gain a dated account of what changed. The reference price supplies market context without establishing anyone’s purchase price, sale price, or profit.

These choices involve
millions of Bitcoin.

The individual reserves hold tens of thousands of Bitcoin. September’s broader reports show why storage behavior deserves attention across the ecosystem.

Quiet reserves keep at least 90% of their balance in amounts held for 90 days or longer. Their monthly movement stays within 10% of opening balance.

The monthly populations change. A fall in the total cannot establish that the same holders sold or moved the difference.

To understand one holder, follow its own history, as in the reserve and treasury examples. Use the aggregate charts to understand the broader storage picture.

How we connect each transfer
to balances and earlier activity

Bitcoin records spent funds and newly created outputs, the amounts a later transaction can spend. Useful intelligence requires connecting those records across time.

TrackBTC builds dated balances, incoming and outgoing histories, and wallet groups linked through transaction evidence.

A wallet group is a unit for following activity. Its relationship to an organization comes from separate attribution evidence.

The work includes tracking which received amounts remain unspent, reconciling balances with fees, and keeping the selected wallet membership consistent within each comparison.

Monthly reports use the addresses assigned to a wallet group at that month’s close. This gives their historical comparisons a consistent set of addresses.

It does not reconstruct which addresses or owners were known at every earlier moment. Each published month keeps its own observation boundary.

We retain the amounts, dates, direction, balances, and price references needed to reproduce these views. The selected published reports remain the source of these examples.

The State Transition Engine article explains how we build this connected history across Bitcoin’s records.

Be the team that can
explain the change.

A useful finding leaves your team with a clear next step. Start with the question, then bring the relevant history and local records together.

Public alerts provide selected examples of activity. Explore the public alerts to see the evidence available without an account.

Our private Intelligence and monthly reports provide wallet histories and comparisons of balances, transfers and counterparties. Contact us about report access for your team.

For a question specific to your operation, choose one workflow for a six-week shadow pilot. We agree the records, cases, and success criteria together.

Historical replay and shadow evaluation let your team review findings alongside its existing work. Transactions, private wallet context, and policies remain in your environment.

The pilot does not change transaction authorization. Its final report records what was checked, what your team validated, and which decisions followed.

That gives colleagues and executives concrete evidence of the work your team initiated. Any joint publication or public acknowledgment requires separate agreement after verification.