How many times to rebroadcast?

[jainy25]

So I have two transaction stuck due to low fees for like 48 hours now. Dropped off blockchain as well. I use Multibit.

I managed to get the hex from another site for one of the transactions and rebroadcast it. For the other one, I can't find the hex anywhere.

Here is the one I got to rebroadcast - https://blockchain.info/tx-index/61ca2e9348fff4166cf25a1144f7fb1fffa0da468992d29c2682ffec19adace2
The other one - https://blockchain.info/tx-index/66c0479bf5788ece1ee086bab04bc524c3f17a358e19f6206afa3808cff4a54f

I am not sure whether the first one could get confirmed soon still. Should I be rebroadcasting it regularly?

And can someone please rebroadcast the second one for me? I just can't find the hex for it..

[1714889962]

1714889962

[1714889962]

1714889962

[1714889962]

1714889962

[mocacinno]

is this what you're looking for?
http://btc.blockr.io/api/v1/tx/raw/66c0479bf5788ece1ee086bab04bc524c3f17a358e19f6206afa3808cff4a54f

0100000002e2acad19ecff82269cd2928946daa0ff1ffbf744115af26c16f4ff48932eca6101000 0006a47304402206429572a7b0c306cd8783e030ff8e17c104facc7830ca8236fa5758af15d6583 02203de82eddaf30504cc44a6fe8c4473af41cc830f8a9cdf265d6cc62c6362d8caa012102044fc 1bad78cfa400aecf07c6aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff0ae79d6df611 32d50ffb350e1fbff861020d837e4973cda427ec5ac741169287010000006b483045022100fc83c 2a2723ab6a7430aa91ed0a7932cb26d911a0c059dfb793dc9eeee3f3dd802207e81f9e54af9df0b f3c0fed960f2ac289bb2ca90940ebc9d16291179b5efa611012102044fc1bad78cfa400aecf07c6 aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff023cac1400000000001976a9145a20a4 d3e7aca3d76c71bc72534a1b1a8cfb70fb88ac31090901000000001976a914b50bb9d83cd287234 d86cfb05e9f1dce199b0d7588ac00000000

I took the liberty of pushing it trough my node, so it's in blockchain.info's mempool again

[jainy25]

is this what you're looking for?
http://btc.blockr.io/api/v1/tx/raw/66c0479bf5788ece1ee086bab04bc524c3f17a358e19f6206afa3808cff4a54f

0100000002e2acad19ecff82269cd2928946daa0ff1ffbf744115af26c16f4ff48932eca6101000 0006a47304402206429572a7b0c306cd8783e030ff8e17c104facc7830ca8236fa5758af15d6583 02203de82eddaf30504cc44a6fe8c4473af41cc830f8a9cdf265d6cc62c6362d8caa012102044fc 1bad78cfa400aecf07c6aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff0ae79d6df611 32d50ffb350e1fbff861020d837e4973cda427ec5ac741169287010000006b483045022100fc83c 2a2723ab6a7430aa91ed0a7932cb26d911a0c059dfb793dc9eeee3f3dd802207e81f9e54af9df0b f3c0fed960f2ac289bb2ca90940ebc9d16291179b5efa611012102044fc1bad78cfa400aecf07c6 aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff023cac1400000000001976a9145a20a4 d3e7aca3d76c71bc72534a1b1a8cfb70fb88ac31090901000000001976a914b50bb9d83cd287234 d86cfb05e9f1dce199b0d7588ac00000000

I took the liberty of pushing it trough my node, so it's in blockchain.info's mempool again

Thanks man!

Any clue how many times it should be rebroadcasted?

I am willing to pay a higher fee. But idk how it can be done. And the way these two transactions are stuck, idk if they will ever go through.

[mocacinno]

is this what you're looking for?
http://btc.blockr.io/api/v1/tx/raw/66c0479bf5788ece1ee086bab04bc524c3f17a358e19f6206afa3808cff4a54f

0100000002e2acad19ecff82269cd2928946daa0ff1ffbf744115af26c16f4ff48932eca6101000 0006a47304402206429572a7b0c306cd8783e030ff8e17c104facc7830ca8236fa5758af15d6583 02203de82eddaf30504cc44a6fe8c4473af41cc830f8a9cdf265d6cc62c6362d8caa012102044fc 1bad78cfa400aecf07c6aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff0ae79d6df611 32d50ffb350e1fbff861020d837e4973cda427ec5ac741169287010000006b483045022100fc83c 2a2723ab6a7430aa91ed0a7932cb26d911a0c059dfb793dc9eeee3f3dd802207e81f9e54af9df0b f3c0fed960f2ac289bb2ca90940ebc9d16291179b5efa611012102044fc1bad78cfa400aecf07c6 aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff023cac1400000000001976a9145a20a4 d3e7aca3d76c71bc72534a1b1a8cfb70fb88ac31090901000000001976a914b50bb9d83cd287234 d86cfb05e9f1dce199b0d7588ac00000000

I took the liberty of pushing it trough my node, so it's in blockchain.info's mempool again

Thanks man!

Any clue how many times it should be rebroadcasted?

I am willing to pay a higher fee. But idk how it can be done. And the way these two transactions are stuck, idk if they will ever go through.

No problem... There is no harm in rebroadcasting a tx every couple of hours, altough it's only actually necessary when the biggest part of the network dropped the tx from their mempool.

Paying a higher fee is tricky. It can be done if you marked the tx as replacable when you created it, altough i'm not sure if the multibit gui already implemented this feature. You could also doublespend the inputs and generate a tx with the same output, but i think that's a very hard thing to do using multibit (since it does not allow you to export your private key, nor allows you to pick your inputs).

What you could attempt is a CPFP: generate a new tx using the unconfirmed outputs of those tx'es as inputs (or the output to your change addy). In this new tx, make sure the fee covers both the old tx and the new tx. This is also a longshot tough, since the miner has to do the effort of calculating wether he could get more fees by adding a low fee and high fee tx to his block.

A last option would be to contact quickseller or macbook-air or kano on  this forum and offer a reward if one of them includes your tx'es in a block they're currently solving.

[jainy25]

is this what you're looking for?
http://btc.blockr.io/api/v1/tx/raw/66c0479bf5788ece1ee086bab04bc524c3f17a358e19f6206afa3808cff4a54f

0100000002e2acad19ecff82269cd2928946daa0ff1ffbf744115af26c16f4ff48932eca6101000 0006a47304402206429572a7b0c306cd8783e030ff8e17c104facc7830ca8236fa5758af15d6583 02203de82eddaf30504cc44a6fe8c4473af41cc830f8a9cdf265d6cc62c6362d8caa012102044fc 1bad78cfa400aecf07c6aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff0ae79d6df611 32d50ffb350e1fbff861020d837e4973cda427ec5ac741169287010000006b483045022100fc83c 2a2723ab6a7430aa91ed0a7932cb26d911a0c059dfb793dc9eeee3f3dd802207e81f9e54af9df0b f3c0fed960f2ac289bb2ca90940ebc9d16291179b5efa611012102044fc1bad78cfa400aecf07c6 aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff023cac1400000000001976a9145a20a4 d3e7aca3d76c71bc72534a1b1a8cfb70fb88ac31090901000000001976a914b50bb9d83cd287234 d86cfb05e9f1dce199b0d7588ac00000000

I took the liberty of pushing it trough my node, so it's in blockchain.info's mempool again

Thanks man!

Any clue how many times it should be rebroadcasted?

I am willing to pay a higher fee. But idk how it can be done. And the way these two transactions are stuck, idk if they will ever go through.

No problem... There is no harm in rebroadcasting a tx every couple of hours, altough it's only actually necessary when the biggest part of the network dropped the tx from their mempool.

Paying a higher fee is tricky. It can be done if you marked the tx as replacable when you created it, altough i'm not sure if the multibit gui already implemented this feature. You could also doublespend the inputs and generate a tx with the same output, but i think that's a very hard thing to do using multibit (since it does not allow you to export your private key, nor allows you to pick your inputs).

What you could attempt is a CPFP: generate a new tx using the unconfirmed outputs of those tx'es as inputs (or the output to your change addy). In this new tx, make sure the fee covers both the old tx and the new tx. This is also a longshot tough, since the miner has to do the effort of calculating wether he could get more fees by adding a low fee and high fee tx to his block.

A last option would be to contact quickseller or macbook-air or kano on  this forum and offer a reward if one of them includes your tx'es in a block they're currently solving.

Seems complicated, and yeah, multibit is pretty restrictive.

I did contact a few people. I hope they could help me out here. I don't mind paying a little more to get these done.