Here's the pushed/broacast-ed tx http://tbtc.blockr.io/tx/info/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080
txid was malleated to txid (when the tx was added into the block):
http://tbtc.blockr.io/tx/info/a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec
I am watching all utx broadcasted on the testnet3 network using https://github.com/bitpay/bitcore-p2p
I did not see a9607981ae4bbf42ed0cfacc05455f9396c85a9e8aeb61474f3f7516c35430ec
broadcast-ed I only saw d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080
How the hell did blockr.io see both the original broadcasted tx and the altered tx when it never was seen on the network?
What voo-doo magic is this?
Look, blockcypher didn't store the original broadcasted txid: https://api.blockcypher.com/v1/btc/test3/txs/d8e5dac095d5f6133e6c3f11e1d9f923c04dac0824f9f8ce0000573df7cc8080
but they did store the malleated version:
HOW?
related: How confirm my own doublespend transaction got confirmed and testnet3 frequent tx malleability