<p>Problem solved, make many sub UTXOs will resolve that well.</p>

CC BY-SA 4.0
2019-09-17T04:29:20.820Z
2019-09-17T04:29:20.820Z
mmo2112
<p>I've started with Bitcoin exchange service, by creating rawtransaction and broadcast it. The problem which I must face to face is too long mempool chain (over 25 unconfirmed transaction). 
<br>
Example: 
<a href="https://bitcoin.stackexchange.com/questions/59178/64-too-long-mempool-chain">64: too-long-mempool-chain</a>
<br>
Using <code>limitancestorcount</code> and <code>limitdescendantcount</code> just resolve on local node, these late txs (transaction after first 25) must wait for a long period time to re-broadcast like this: <br>
<a href="https://bitcoin.stackexchange.com/questions/51255/transaction-not-found-in-blockchain/51256#51256">Transaction not found in Blockchain</a>
<br>
Here is my testnet address has many unconfirmed txs and still pending hold, if I search on another explorer, I can't see 45 unconfirmed txs, same to <code>getrawtransaction</code> on node, response is <code>No such mempool or blockchain transaction</code>:
<br>
<a href="https://live.blockcypher.com/btc-testnet/address/mxHqrQBWuCndNaubTYUbcEVzeNPsT34TP6/" rel="nofollow noreferrer">https://live.blockcypher.com/btc-testnet/address/mxHqrQBWuCndNaubTYUbcEVzeNPsT34TP6/</a>
<br>
So, how can I avoid this issue, I just think few ways such as: Divide main address to few sub addresses which divides main UTXO to few UTXOs, create many-to-many transaction (currently is 1-2, 1 target and 1 changeAddress back), using high confirmation UTXO first,... Which options can bring better result and performance for a long time scaling up? Any advice is really appreciate. And last question, is there anyway to mark 1 UTXO that is used for 25 times (example I use UTXO X first, then it's returned Y, use Y is returned Z, total using X = 2, I don't have any related information to calculate it because node returns UTXO contains only txId). </p>

<bitcoin-core><mempool>
Resolve BTC long mem pool (many unconfirmed tx)
mmo2112
# Resolve BTC long mem pool (many unconfirmed tx)

(Asked by: username_0 on 2019-09-12)

I've started with Bitcoin exchange service, by creating rawtransaction and broadcast it. The problem which I must face to face is too long mempool chain (over 25 unconfirmed transaction).
  
Example:
[64: too-long-mempool-chain](https://bitcoin.stackexchange.com/questions/59178/64-too-long-mempool-chain)
  
Using `limitancestorcount` and `limitdescendantcount` just resolve on local node, these late txs (transaction after first 25) must wait for a long period time to re-broadcast like this:   
[Transaction not found in Blockchain](https://bitcoin.stackexchange.com/questions/51255/transaction-not-found-in-blockchain/51256#51256)
  
Here is my testnet address has many unconfirmed txs and still pending hold, if I search on another explorer, I can't see 45 unconfirmed txs, same to `getrawtransaction` on node, response is `No such mempool or blockchain transaction`:
  
<https://live.blockcypher.com/btc-testnet/address/mxHqrQBWuCndNaubTYUbcEVzeNPsT34TP6/>
  
So, how can I avoid this issue, I just think few ways such as: Divide main address to few sub addresses which divides main UTXO to few UTXOs, create many-to-many transaction (currently is 1-2, 1 target and 1 changeAddress back), using high confirmation UTXO first,... Which options can bring better result and performance for a long time scaling up? Any advice is really appreciate. And last question, is there anyway to mark 1 UTXO that is used for 25 times (example I use UTXO X first, then it's returned Y, use Y is returned Z, total using X = 2, I don't have any related information to calculate it because node returns UTXO contains only txId).

**Tags:** bitcoin-core, mempool


---

## 1 answers

### Answer by username_0 on 2019-09-17. Score: 0 | Accepted answer

Problem solved, make many sub UTXOs will resolve that well.


---

