> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/advanced/coin-control.md).

# Coin control

How to use coin control in Cake Wallet to view, label and freeze outputs on Bitcoin, Litecoin, Monero and other wallets, or pick which coins fund a single send.

When you receive Bitcoin (or several other coins), your balance isn't one big pool — it's a collection of individual "outputs," like separate bills in a wallet. Coin control lets you see those outputs and choose which ones a transaction spends. That matters for privacy: it keeps coins you'd rather not link together — say, a KYC exchange withdrawal and a private payment — from being spent in the same transaction.

Coin control is available for Bitcoin, Litecoin, Bitcoin Cash, Dogecoin, Monero, and Decred wallets. On Bitcoin wallets with several [accounts](https://docs.cakewallet.com/cryptos/bitcoin#accounts), coin control shows the active account's coins only.

## View your coins

{% stepper %}
{% step %}

### Open Coin Control

Open `Settings` from the top right of the home screen, tap your wallet's coin settings (for example `Bitcoin Settings`), then `Coin Control`.

![Bitcoin Settings with the Coin Control row](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.5.0/settings_btc_01_coin-settings_hl-2.png)
{% endstep %}

{% step %}

### Review your outputs

Each row is one output: its amount and the address it was received on. Tap an output to see its details.

![Coin Control list showing one unspent output](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/coincontrol_02_list_hl.png)
{% endstep %}

{% step %}

### Label or freeze an output

The details screen shows the output's amount, transaction ID, and address. Add a note so you remember where it came from ("exchange withdrawal", "paid by Alice"), or flip the `Freeze` toggle to stop it from being spent.

![Unspent coins details with Freeze toggle](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/coincontrol_03_utxo-details_hl.png)
{% endstep %}

{% step %}

### Frozen coins stay put

Frozen outputs move under a `Frozen` header and are never spent — they show up in your unavailable balance until you unfreeze them. Freezing is persistent across all transactions until you change it.

![Coin Control list with a frozen output](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/coincontrol_05_list-frozen.png)
{% endstep %}
{% endstepper %}

## Choosing coins for a single transaction

You don't have to freeze coins to control one payment: the Send and Swap screens also let you filter which outputs that one transaction may use, without changing anything permanently. Look for `Coin Control` under the Send screen's `Advanced Settings`.

{% hint style="info" %}
If your available balance looks lower than expected, check here first — frozen outputs are excluded from what you can spend. See [Why is my Available Balance 0?](https://docs.cakewallet.com/faq/zero-balance) for other causes.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/features/advanced/coin-control.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
