How Blockchain Sleuths Trace Poker Change Outputs

Every Bitcoin transaction that doesn’t spend an input exactly needs somewhere to send the leftover value, and that leftover almost always comes back to the sender as a “change” output. Because change outputs are functionally different from payment outputs but look identical on the blockchain—just another output with an address and an amount—blockchain analysis firms have spent years building heuristics specifically to tell them apart.

Identifying the change output matters because it lets an analyst treat that output as the same wallet continuing forward into its next transaction, effectively stitching together a chain of activity that would otherwise look like separate, unrelated addresses. For a poker player moving cryptocurrency in and out of a wallet used for deposits and payouts, this is the mechanism that most directly threatens the assumption that on-chain activity is hard to link to a real identity.

This guide breaks down how change-detection heuristics actually work, what they can and can’t reveal, and what practically defeats them.

Understanding UTXO Change Outputs

Bitcoin’s UTXO model means every transaction consumes whole, discrete outputs as inputs—there’s no concept of a running account balance to draw a partial amount from. If your wallet holds a single UTXO worth more than the amount you want to send, the transaction must spend that entire UTXO, sending the intended amount to the recipient and the remainder back to an address you control as change.

From the blockchain’s perspective, a transaction with two outputs offers no explicit label saying which one is the payment and which is the change. Both are just addresses receiving amounts. This ambiguity is exactly what change-detection heuristics are built to resolve, using patterns in how ordinary wallet software behaves.

The reason this matters at all is that most wallets generate a fresh, previously unused address for change automatically, while the payment output usually goes to an address chosen or provided by someone else entirely—two outputs from the same transaction that, once separated, can be traced down very different paths.

How Analysts Identify the Change Output

No single heuristic works reliably alone, but combined, they let analysts assign a confidence score to each output in a transaction rather than a simple guess.

The Script-Type Matching Heuristic

Wallet software typically generates change addresses using the same script type as its own inputs—if the inputs are native SegWit addresses, the change output usually is too. When a transaction’s inputs are one script type and one output matches that type while the other doesn’t, the matching output is statistically more likely to be change, since the payment recipient may use different wallet software entirely.

The Round-Number Heuristic

Humans tend to request or send round amounts—an even number of dollars converted to BTC, for instance—while the resulting change is whatever awkward remainder is left over after fees and the round payment are subtracted. An output with a suspiciously round value is more likely the intended payment; the other, non-round output is more likely change.

The Address Reuse Heuristic

If one output address has never appeared on the blockchain before while the other has transaction history, the fresh address is statistically more likely to be wallet-generated change, since payment recipients—especially services and exchanges—more often reuse known deposit addresses.

What This Means for Player Privacy

Once a change output is correctly identified, it becomes the starting point for the next transaction in the same wallet’s history, and the process repeats. Chained across enough transactions, this builds a cluster of addresses that analysts treat as controlled by a single entity—without ever needing to compromise wallet security or access private keys directly.

This is why blockchain transactions are described as pseudonymous rather than anonymous: the addresses themselves carry no name, but the pattern of how they’re used can link them together, and if any single address in the cluster is ever tied to an identity—through an exchange’s KYC records, for example—the entire cluster inherits that identification.

Common Mistakes Players Make

• Assuming a new address for every transaction fully prevents clustering, when heuristics link addresses by behavior, not just reuse
• Consolidating poker winnings and unrelated funds into the same wallet, merging two activity histories into one traceable cluster
• Using round, easily-flagged withdrawal amounts that make payment-versus-change identification more reliable for an observer
• Sending withdrawals directly to an exchange address already tied to a verified identity, then treating the rest of the wallet as separate

Advanced Clustering and Deanonymization Techniques

The Common-Input-Ownership Heuristic

When a transaction spends multiple inputs at once, the standard assumption is that all of those inputs are controlled by the same wallet, since a normal wallet needs to sign for every input it spends. This heuristic is separate from change detection but compounds with it—clustering inputs together, then following the identified change output forward, multiplies how much of a wallet’s history becomes linkable from a single transaction.

Multi-Hop Tracing

Once a cluster is established, analysts follow funds across multiple subsequent transactions, applying the same heuristics at each hop. Funds don’t need to move directly between two addresses to be traced—a chain of several transactions through intermediate change outputs can still be reconstructed end to end.

Exchange Deposit Correlation

Timing and amount correlation between a withdrawal from one service and a deposit to another—even without any heuristic linking specific addresses—can strengthen an analyst’s confidence that two clusters belong to the same person, particularly when the amounts and timing line up closely.

No individual defense is complete on its own; privacy-focused wallet behavior generally combines several of these countermeasures at once rather than relying on a single fix.

Tracing a Poker Withdrawal Through Change Outputs

A player withdraws winnings to a personal wallet, then later moves a portion of those funds to an exchange to convert to fiat.

• The withdrawal transaction has two outputs: the amount sent to the player’s wallet and a change output back to the platform’s own reserve
• The player’s incoming address has no prior transaction history, matching the address-reuse pattern for a freshly received payment
• Weeks later, the player sends a portion of that balance to an exchange, creating a new transaction with its own payment and change outputs
• The exchange deposit address is already associated with the player’s verified account through standard KYC records

The Technical Process

An analyst applies the script-type and round-number heuristics to the second transaction to correctly separate the exchange deposit from the player’s own change output, then links that change output forward to whatever the player does with it next.

The Outcome

Because the exchange deposit is already tied to a real identity through KYC, the entire cluster of addresses connected through the identified change outputs inherits that identification—including the original withdrawal from the poker platform, even though that transaction alone carried no identifying information.

How Privacy-Conscious Players Break These Heuristics

Experienced users of the ACR Poker software deliberately avoid patterns heuristics rely on: generating fresh addresses consistently, avoiding round withdrawal amounts, and keeping funds destined for different purposes in separate wallets rather than one consolidated balance that merges unrelated activity into a single traceable cluster.

Using PayJoin to Break Common-Input-Ownership

PayJoin transactions have both the sender and recipient contribute inputs, directly violating the assumption that all inputs in a transaction share one owner. This specifically targets the common-input-ownership heuristic, though it requires wallet software on both ends to support the protocol.

The Future of Change Output Privacy

Taproot’s uniform output appearance already reduces how easily script-type heuristics distinguish outputs, since Taproot transactions look structurally similar regardless of the spending conditions behind them. Proposed protocols like silent payments aim to remove the need for on-chain address reuse entirely, generating a fresh receiving address per transaction without any coordination between sender and recipient.

These developments raise the cost of clustering analysis but don’t eliminate it—metadata like timing, amounts, and network-level transaction broadcast patterns remain separate privacy considerations that heuristic-based address clustering alone doesn’t address.