user61002: I'm creating a web page to monitor bitcoin mempool https://mempoolexplorer.com/ and I've realized that sometimes exists huge transactions dependency graphs in the mempool.
I'm talking about +-700 transactions which depends among them, and although no mempool rule is broken, i.e. max mempool ancestors for a transaction, I'm puzzled about what can be doing this kind of dependency graphs.
I've stored some graphs in json format: https://gist.github.com/dev7ba/c144c68127b97082652bc860cc95edf6 and https://gist.github.com/dev7ba/50167d6e336100698ab2599123444efc that contains some examples of those graphs.
Those gists .json are created by the backend of my web page that you can call it here: https://mempoolexplorer.com/txmempool/miningQueueAPI/tx/{txIdHere} to obtain a transaction statistics currently in mempool. See txDependenciesInfo.nodes and txDependenciesInfo.edges data to obtain the dependency info.
Also, as it's difficult to obtain a transaction with dependencies, I've created a section https://mempoolexplorer.com/txsGraphs or https://mempoolexplorer.com/txmempool/miningQueueAPI/txGraphList which lists all the dependency graphs that exists currently in the mempool, with the transactions set, and whether the graph is linear or not (i.e. using Child Pays For Parent several times instead of BIP-125).
Be aware that mempool is refreshed in the back-end each 5 seconds. But if the mempool is too large:  >30000 transactions, graphs calculation will be omitted to avoid high overload.
Thanks.

user61002: The most plausible answer is that those graphs are caused by wallets when there is not enough available UTXOs for the amount of recipients.
i.e. If you only have 2 UTXOs and you have to make 10 payments at the same time, wallets uses the unconfirmed UTXOs as TX inputs, creating those dependency graphs.

61002: <p>I'm creating a web page to monitor bitcoin mempool <a href="https://mempoolexplorer.com/" rel="nofollow noreferrer">https://mempoolexplorer.com/</a> and I've realized that sometimes exists huge transactions dependency graphs in the mempool.</p>
<p>I'm talking about +-700 transactions which depends among them, and although no mempool rule is broken, i.e. max mempool ancestors for a transaction, I'm puzzled about what can be doing this kind of dependency graphs.</p>
<p>I've stored some graphs in json format: <a href="https://gist.github.com/dev7ba/c144c68127b97082652bc860cc95edf6" rel="nofollow noreferrer">https://gist.github.com/dev7ba/c144c68127b97082652bc860cc95edf6</a> and <a href="https://gist.github.com/dev7ba/50167d6e336100698ab2599123444efc" rel="nofollow noreferrer">https://gist.github.com/dev7ba/50167d6e336100698ab2599123444efc</a> that contains some examples of those graphs.</p>
<p>Those gists .json are created by the backend of my web page that you can call it here: <a href="https://mempoolexplorer.com/txmempool/miningQueueAPI/tx/%7BtxIdHere%7D" rel="nofollow noreferrer">https://mempoolexplorer.com/txmempool/miningQueueAPI/tx/{txIdHere}</a> to obtain a transaction statistics currently in mempool. See <code>txDependenciesInfo.nodes</code> and <code>txDependenciesInfo.edges</code> data to obtain the dependency info.</p>
<p>Also, as it's difficult to obtain a transaction with dependencies, I've created a section <a href="https://mempoolexplorer.com/txsGraphs" rel="nofollow noreferrer">https://mempoolexplorer.com/txsGraphs</a> or <a href="https://mempoolexplorer.com/txmempool/miningQueueAPI/txGraphList" rel="nofollow noreferrer">https://mempoolexplorer.com/txmempool/miningQueueAPI/txGraphList</a> which lists all the dependency graphs that exists currently in the mempool, with the transactions set, and whether the graph is linear or not (i.e. using Child Pays For Parent several times instead of BIP-125).</p>
<p>Be aware that mempool is refreshed in the back-end each 5 seconds. But if the mempool is too large:  &gt;30000 transactions, graphs calculation will be omitted to avoid high overload.</p>
<p>Thanks.</p>
 61002: <p>The most plausible answer is that those graphs are caused by wallets when there is not enough available UTXOs for the amount of recipients.</p>
<p>i.e. If you only have 2 UTXOs and you have to make 10 payments at the same time, wallets uses the unconfirmed UTXOs as TX inputs, creating those dependency graphs.</p>
