# Why is there more than one input on my BTC transactions?

Even though Freewallet is showing you the correct total amount of BTC in your wallet <mark style="color:yellow;">it may be that you have many Unspent Transaction Output’s (UTXO) that make up your total amount of BTC in your wallet.</mark>\
\
This naturally happens over time especially if you have done many counterparty transactions (small BTC transactions) and accumulate many UTXO’s on your address.

If you would like to learn more about this process and its relation to Counterparty and Freewallet (and have some time read and understand it) [this medium article explains in detail](https://medium.com/@davesta.xcp/understanding-btc-fees-and-utxos-when-using-counterparty-ae22f40b642a) what UTXO's are, how to view and manage them and their relation to Freewallet.

<figure><img src="/files/3MCGX1Z8AuYIBkc0ExKl" alt=""><figcaption><p>Medium article that explains in depth what UTXO's are and their relation to Freewallet transactions</p></figcaption></figure>

If you see more than one input from your address on a block explorer for a BTC transaction it most likely just means you had to use more than one UTXO on your address. \
\
Here is an example of a Bitcoin address with more than one "input" (or UTXO) on it as viewed on Blockchain.info

<figure><img src="/files/GcAkV4zoYr1mRAmXGpoX" alt=""><figcaption><p>An address with 6 UTXO's that make up the total amount of BTC on the address</p></figcaption></figure>

It is very common for not only Counterparty users, but also all Bitcoin users in general to consolidate these UTXO's by sending all of the Bitcoin on the address back to the same address it is on.&#x20;

This process and best way to consolidate UTXO's is [explained in the medium article mentioned before](https://medium.com/@davesta.xcp/understanding-btc-fees-and-utxos-when-using-counterparty-ae22f40b642a).

When it comes to the topic of [MPMA sends (Multi-sends) using Freewallet](/freewallet.io-user-manual/freewallet-functions/using-the-multi-send-function.md) and how extra outputs are used. These MPMA sends use Counterparty encoded send data within the Transaction data. \
\ <mark style="color:yellow;">These extra outputs are NOT send destinations.</mark>

<figure><img src="/files/XEpfyFKzBSPzumAqZRuU" alt=""><figcaption><p>Example Multi-Send as shown on Tokenscan.io</p></figcaption></figure>

Above is an example large-scale MPMA send using Counterparty. On Tokenscan the <mark style="color:red;">Transaction Hash</mark> is shown above with the Red Box and the Source address is shown with the Blue Box.\
\
You may see on a BTC explorer that extra outside addresses not related to your address are being included, just like this transaction above.\
\
Below is that exact same <mark style="color:red;">Transaction Hash</mark>, but shown on mempool.space with 'strange' inputs from addresses that start with a "3".

<figure><img src="/files/mCMzCJzfNmkhPC0IfSfJ" alt=""><figcaption></figcaption></figure>

Multi-Sends work by encoding data into two transactions and having strange addresses (like addresses that start with "3") is not uncommon to see when looking over your transaction on a BTC block explorer. These are included in the fee when broadcasting the MPMA Counterparty send.\
\
How many extra output addresses are included depends entirely on the amount of data encoded in the MPMA send. It is important to note here that the data shown on Tokenscan for your multi-send is showing the accurate destinations that the multi-sends are being forwarded to.&#x20;

<mark style="color:yellow;">The underlying tech is the reason you are seeing more outputs on a BTC block explorer.</mark>

If you are seeing the error "Failure to send not enough BTC in wallet" when you absolutely have enough BTC to cover your transaction it could be that this error is in relation to your UTXO’s on your address and [please reference this guide](/freewallet.io-user-manual/troubleshooting-issues/failure-to-send-not-enough-btc-in-wallet.md) in the Common Freewallet Errors section.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://davestaxcp.gitbook.io/freewallet.io-user-manual/common-questions-using-freewallet-faq/why-is-there-more-than-one-input-on-my-btc-transactions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.