Normal lookup
Address
Balance
Transactions
Bitcoin intelligence reports
The Shape of Bitcoin
Bitcoin activity is not just address, balance, and transaction history. It is addresses, unspent outputs, spent outputs, timing, clustering, velocity, fan-in, fan-out, and custody behavior. TrackBTC reports are built around that shape.
What the chain actually shows
Outputsspent / unspent
Wallet surfacemany addresses
Flowfan-in / fan-out
Behaviormovement / storage
Evidenceaddresses / txs / members
Bitcoin activity has shape.
The same BTC amount can mean different things depending on output size, age, velocity, address footprint, and whether value is being gathered, routed, retained, or left still. That is why TrackBTC reports start with behavior before asking an analyst to inspect exact evidence.
Address count
UTXO count
Output size
Age
Velocity
Spent history
Fan-in
Fan-out
Clustering
Script format
Bitcoin is not an account system.
Bitcoin works through transaction outputs. When an output has not been spent, it is a UTXO: an unspent transaction output. A wallet balance is usually the sum of many UTXOs, not one ledger row.
A Bitcoin balance is not one number. It is a shape.
Wallet balance: 12.4 BTC
12.4 BTC
11.14
1.00
0.21
0.05
The visible balance hides the inventory shape that matters for fees, flexibility, and operational review.
Addresses are surfaces, not identities.
A Bitcoin address is a receiving destination. It is not automatically a person, company, exchange, or wallet. One operator can use many addresses; one address can be a deposit surface, hot wallet, cold wallet, sweep point, or temporary staging point.
The address is the surface. The behavior is the signal.
One operating system can expose many surfaces
Wallet group
Deposit addresses
Sweep wallet
Hot wallet
Batching wallet
Cold storage
Change outputs
Cluster-level evidence helps move from isolated lookup pages to operational shape without pretending that every address is a confirmed identity.
Address format is metadata. Behavior is intelligence.
Script and address format can hint at wallet age, infrastructure choices, or signing style, but format alone is not enough. The useful signal comes from how addresses are used over time.
1...Legacy P2PKHOften older wallet or software patterns.
3...P2SHCan include wrapped SegWit, multisig-style use, or older service infrastructure.
bc1q...Native SegWitModern standard wallet behavior with lower fee weight.
bc1p...TaprootNewer script path and signing behavior, useful as context but not attribution.
UTXOs are the real inventory.
A wallet with 10 BTC might hold one clean output or thousands of tiny outputs. Those two states have the same headline balance, but very different fee exposure and operational pressure.
Concentrated inventory
10 BTC
Simple to read, but a partial spend creates change and can require more policy coordination when the output is large.
Fragmented inventory
0.0010.0010.0010.0010.001x10k
Cheap to receive into, but expensive to clean up when fees rise because each spend consumes many inputs.
The reports turn shape into ranked behavior.
The public alert stream and report products start from four practical behavior families. Each family asks a different question about how Bitcoin moved, stayed, gathered, or sat still during the report window.
Movement
Which wallet groups moved meaningful BTC quickly through the window?
Useful for routing, treasury movement, exchange-style flow, and high-throughput pass-through review.
Retention
Which wallet groups received BTC and still held much of it at the report block?
Useful for accumulation, reserve posture, and distinguishing flow-through from held value.
Storage
Which wallet groups show large visible balances with low outgoing activity?
Useful for storage-like posture, custody review, treasury surfaces, and stale-balance monitoring.
Consolidation
Which wallet groups gathered fragments or reorganized wallet surfaces?
Useful for deposit sweeps, UTXO cleanup, operational reshuffles, and fan-in event review.
Fan-in, fan-out, and spent history reveal operations.
Current UTXOs show state. Spent outputs show behavior. The history tells whether value was received, held, merged, split, withdrawn, routed, or cleaned up.
Deposits and sweeps
Client A
Client B
Client C
Deposit
Sweep wallet
Cold / hot
Many addresses with similar receive-and-sweep behavior can signal deposit infrastructure.
Withdrawals and payouts
Service wallet
User 1
User 2
Change
User 3
User 4
Withdrawal transactions often look like fan-out. Deposit sweeps often look like fan-in.
Consolidation pressure
Small UTXOs
High inputs
Fewer outputs
Fee risk
Cleanup
New posture
Fragmented wallets can become expensive to operate during fee spikes, so cleanup itself becomes a signal.
Custody is slow because movement is controlled.
Large custody systems move slowly because moving BTC is a risk event. Policy, signing infrastructure, HSM access, approvals, batching, compliance, liquidity management, fee selection, and monitoring can all shape the on-chain footprint.
RequestA movement or withdrawal is initiated.
PolicyLimits, approvals, and allowed destinations are checked.
RiskCompliance, fraud, and operational risk controls run.
LiquidityFunds may move from cold, warm, or hot wallet layers.
SigningSigner, HSM, or quorum workflows authorize the transaction.
BroadcastBatching, fee policy, and monitoring finish the movement.
Large, slow-moving outputs often signal coordination, not inactivity.
TrackBTC turns Bitcoin state into usable intelligence.
A normal block explorer helps you look up Bitcoin data. TrackBTC is built to explain the structure around it: address behavior, UTXO shape, spent-output history, fan-in and fan-out flows, deposit-like behavior, withdrawal-like behavior, consolidation events, retained balances, velocity, storage posture, and cluster-level evidence.
The useful question is not only what happened in this transaction. The useful question is what kind of system this transaction belongs to.