Transaction Can't Be Found?!

[TruCoinz]

Hey,

I'm having problems with this transaction taking forever (did this transaction on 21/12/17) as it is but on top of the issues i'm having with my wallet and this transaction it's not found when searching on https://blockchain.info

The address I sent it to shows up but the TXID doesn't, anyone know why this might be happening?!

Thanks

[jackg]

Hey,

I'm having problems with this transaction taking forever (did this transaction on 21/12/17) as it is but on top of the issues i'm having with my wallet and this transaction it's not found when searching on https://blockchain.info

The address I sent it to shows up but the TXID doesn't, anyone know why this might be happening?!

Thanks

Usually because it dropped from the mempool, done normally under 2 circumstances:
1. The fee is very low and gets pushed out by another transaction with a slightly higher fee as there is a size limit in the mempool.
2. 21+ days elapsed (which obviously didn't occur).

Is there anything else that could have provoked this? Could you just resign the transaction ensuring the same inputs are used. Also if you can get the TX or raw transaction hash, I could attempt to rebroadcast it for you.

[TruCoinz]

Usually because it dropped from the mempool, done normally under 2 circumstances:
1. The fee is very low and gets pushed out by another transaction with a slightly higher fee as there is a size limit in the mempool.
2. 21+ days elapsed (which obviously didn't occur).

Is there anything else that could have provoked this? Could you just resign the transaction ensuring the same inputs are used. Also if you can get the TX or raw transaction hash, I could attempt to rebroadcast it for you.

Hey, I'd imagine it could be the first point as I stupidly put a very low fee. I get the following when asking for the raw transaction:
02000000032055ce1a54c41862a98f7a054d555a292381235f28e89dc5e7ec448a6eadb92e01000 0006b483045022100c6fdf013ec8a3dca5f0a3d8736bab84c3dc84a81d1419b64fd9976abf309c6 56022038854ec8a4ecffae88f71f1e2b6aca51d31adad63ebfc9733f87bf8eb6020ade01210246c 563402341faa36707270ba16890de87f78a489ee11ee2d2cad1f485cd26c0feffffff5fd5fcfb4e 99738d0c8d3ae79abd19ff34c88656670f051119fb1db4149f08a2010000006a473044022050d01 a6fd8e4a00eb6fa55a4409c48efacc547c771ab0f5ef4a46b1c40853a690220799d67094943b63e 5721f937d7ab23e38e3fe493cb25a6f6b519c815d2f8306301210246c563402341faa36707270ba 16890de87f78a489ee11ee2d2cad1f485cd26c0feffffff680595556c6d661550ea983db5449dc9 dddc09409e18e3f76601b2505dcb04d0010000006b4830450221008c65a5d2a285f6cfeae8b713c 02f7935336d11c779d4a4d10681a0a26018abca022016b4b6179f33ae0ea2a0c93a91f4902c4ba2 78fc6e30a4b059b35141b1be214c012103cccc2ca52263306c2a0b69004930c16a9c33ea0202437 fc030f51e723cee30aafeffffff0130220f00000000001976a914620fd2e96f3e188314caf85219 78cbf6f820e35c88acb2a20700

I'm not aware of anything else that could've provoked this (other than my wallet crashing). Sorry if this sounds stupid but how would I go about resigning the transaction


Thanks

[HCP]

Your problem is that the transaction is using a fee of ~1 sat/byte (total paid: 0.00000488 sats, transaction size 487 bytes)

You'll be lucky if any nodes relay this transaction... pretty much all the nodes I tried to send through responsed "Error-66: mempool min-fee not met". You should just let this transaction "die", and recreate it from your wallet, but use a "proper" fee.