user14319: Is there a quick and dirty way to detect all transactions whose tx-id can be found in more than one transaction since the genesis block? 
I would also like to see mutated transactions as well although I am not sure if the blockchain keeps a historical track of the mutated transactions.

user2306: 
Is there a quick and dirty way to detect all transactions whose tx-id can be found in more than one transaction since the genesis block?

There are multiple ways to read your question.
Are there cases where the same transaction has been included into the blockchain multiple times?
Yes. There is one recorded instance of the same coinbase appearing twice. The problem this causes is that only one of these can be redeemed. It also makes it possible to reduce a fully-confirmed transaction to one confirmation, though I don't understand the details. BIP34 fixed this.
Are there cases where the same input hash appears in multiple transactions?
Yes. It happens all the time. For example, transaction 9fa3... has two outputs. Those two outputs were spent by two different transactions. Each transaction needed to include the same input hash (though the vout field was different.)
Are there are any known collisions in SHA256?
No.

I would also like to see mutated transactions as well although I am not sure if the blockchain keeps a historical track of the mutated transactions.

It doesn't.

14319: <p>Is there a quick and dirty way to detect all transactions whose <code>tx-id</code> can be found in more than one transaction since the genesis block? </p>

<p>I would also like to see mutated transactions as well although I am not sure if the blockchain keeps a historical track of the mutated transactions.</p>
 2306: <blockquote>
<p>Is there a quick and dirty way to detect all transactions whose tx-id can be found in more than one transaction since the genesis block?</p>
</blockquote>
<p>There are multiple ways to read your question.</p>
<h3>Are there cases where the same transaction has been included into the blockchain multiple times?</h3>
<p><a href="https://blockexplorer.com/block/00000000000743f190a18c5577a3c2d2a1f610ae9601ac046a38084ccb7cd721" rel="nofollow noreferrer">Yes</a>. There is one recorded instance of the same coinbase appearing twice. The problem this causes is that only one of these can be redeemed. It also makes it possible to reduce a fully-confirmed transaction to one confirmation, though I don't understand the details. <a href="https://github.com/bitcoin/bips/blob/master/bip-0034.mediawiki" rel="nofollow noreferrer">BIP34</a> fixed this.</p>
<h3>Are there cases where the same input hash appears in multiple transactions?</h3>
<p>Yes. It happens all the time. For example, transaction <a href="https://blockchain.info/tx/9fa3d63d7a251da39c3785f7140975c96d5c985889d0867042dddc4be5218cc3" rel="nofollow noreferrer">9fa3...</a> has two outputs. Those two outputs were spent by two different transactions. Each transaction needed to include the same input hash (though the vout field was different.)</p>
<h3>Are there are any known collisions in SHA256?</h3>
<p>No.</p>
<blockquote>
<p>I would also like to see mutated transactions as well although I am not sure if the blockchain keeps a historical track of the mutated transactions.</p>
</blockquote>
<p>It doesn't.</p>
