Author

Topic: Somebody broadcast this TX for me!!! (Read 1563 times)

sr. member
Activity: 714
Merit: 251
November 23, 2016, 11:09:24 PM
#13
newbie
Activity: 19
Merit: 0
November 23, 2016, 09:33:25 PM
#12

Code:
01000000019b74217484881530c4d43ba69839895c7fc85867c0bd2fde62e70ddea598c4ed0100000069463043022028cdacd58b145db882c478029c27b605237869657a49a4f30062ed3619881b09021f68ee0065f8666673dac1d2482bcb130f6c31d68ac6d687856d158b7d669491012102a68215689362729db9ad56f431235a5d3e76f8695630e98c1d759d0662f77621ffffffff0158d31a00000000001976a91461ba1c4beea5a5ce2c8941f0237b378a124189f188ac00000000

Can someone push it from a Full Bitcoin Wallet?

I try with electrum wallet connected to server electrum.hsmiths.com . In the gui i use the menu: Tools -> Load Transaction -> From text

4 confirmations worked? https://blockchain.info/tx/7781e09ef814ca0ebff9e486ea8f2e6e79d86dd581172ba963455d82cf189656
sr. member
Activity: 714
Merit: 251
November 23, 2016, 08:39:05 PM
#11

If you're only sending from 161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM however you'll just have to wait a little bit more (it's already possible if you use a full node). That is unless someone rebroadcast the 2 transactions.

Ok forget about the  14sWMKqX43Rdjr8kzqxjkKYc5h3MA79fuo

What can I do about the 2 transactions from  161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM , they are in limbo for 72 hours.

I have made a double spend transaction to swipe the balance and send it to another address that should cancel the 2 pending TX, can somebody broadcast it successfully?

Try https://blockr.io/tx/push .

I cant, all these fucking block explorers don't let double spends through

Quote
There was an error pushing your transaction to network!

Did you sign your transaction? Is this double spend? Have you already sent this transaction?

Code:
01000000019b74217484881530c4d43ba69839895c7fc85867c0bd2fde62e70ddea598c4ed0100000069463043022028cdacd58b145db882c478029c27b605237869657a49a4f30062ed3619881b09021f68ee0065f8666673dac1d2482bcb130f6c31d68ac6d687856d158b7d669491012102a68215689362729db9ad56f431235a5d3e76f8695630e98c1d759d0662f77621ffffffff0158d31a00000000001976a91461ba1c4beea5a5ce2c8941f0237b378a124189f188ac00000000

Can someone push it from a Full Bitcoin Wallet?
hero member
Activity: 629
Merit: 501
Experientia docet
November 23, 2016, 08:35:06 PM
#10

If you're only sending from 161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM however you'll just have to wait a little bit more (it's already possible if you use a full node). That is unless someone rebroadcast the 2 transactions.

Ok forget about the  14sWMKqX43Rdjr8kzqxjkKYc5h3MA79fuo

What can I do about the 2 transactions from  161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM , they are in limbo for 72 hours.

I have made a double spend transaction to swipe the balance and send it to another address that should cancel the 2 pending TX, can somebody broadcast it successfully?

Try https://blockr.io/tx/push .
sr. member
Activity: 714
Merit: 251
November 23, 2016, 08:20:51 PM
#9

If you're only sending from 161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM however you'll just have to wait a little bit more (it's already possible if you use a full node). That is unless someone rebroadcast the 2 transactions.

Ok forget about the  14sWMKqX43Rdjr8kzqxjkKYc5h3MA79fuo

What can I do about the 2 transactions from  161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM , they are in limbo for 72 hours.

I have made a double spend transaction to swipe the balance and send it to another address that should cancel the 2 pending TX, can somebody broadcast it successfully?
hero member
Activity: 629
Merit: 501
Experientia docet
November 23, 2016, 08:11:09 PM
#8
No, Look I have 3 unconfirmed transactions from 2 addresses.

What I am trying to do is to sweep the 2 addresses clean and send the money to a new address. It would cancel the 3 unconfirmed ones.

Then I will rebroadcast the 3 transactions into 1 merged one with big fee.

You won't be able to do that without a miner because the first input is still fresh and most likely exists in most nodes mempool. The new transaction will be rejected by every single one of them as double spend. Meaning you'll have to wait longer.
Besides, the transaction from 14sWMKqX43Rdjr8kzqxjkKYc5h3MA79fuo paid 54 satoshi per byte fee. That won't take very long.

If you're only sending from 161dqUpmLZ5qzkFZrzcaSQEStKBD3XYVrM however you'll just have to wait a little bit more (it's already possible if you use a full node). That is unless someone rebroadcast the 2 transactions.
sr. member
Activity: 714
Merit: 251
November 23, 2016, 07:55:56 PM
#7

It doesn't let me there, it says that the input is spent, but it's not, its unconfirmed for 72 hours.

It is.
https://blockchain.info/tx/390a7750e3cde8dea1b5b7f6963c2c222c9b1c7c36128b560ee27ecea1531bde

I doubt that transaction have been there for 72 hours. Fee is 54 satoshi per byte and the input have 40 confirmation and 80 per byte fee. Could be wrong though.

Whatever the case is. It'll be best to let that transaction confirm.

Not that one, the other TXs are the older ones, should I just double spend the other 2 without that one?

3977f189d1533a6519df92ea61aeef792434de939d620f7d11996561e273206e
73535a439f2ad97efa7998923a91bfbe4b11bd9338e048aa989b751a9e170179

?

That hex you posted spends an input from 633d4aa816d1c077375cea57f05f4a92010c3f52a753823989e820ec478d10fe:1 and edc498a5de0de762de2fbdc06758c87f5c893998a63bd4c4301588847421749b:1 .

You got the input transactions wrong.

Edit:
Sorry. I misunderstood. You got the input right. But the first input doesn't have anything to do with those two transactions you posted so it's not needed and it won't get dropped by the network just yet (it'll probably confirm before that).

No, Look I have 3 unconfirmed transactions from 2 addresses.

What I am trying to do is to sweep the 2 addresses clean and send the money to a new address. It would cancel the 3 unconfirmed ones.

Then I will rebroadcast the 3 transactions into 1 merged one with big fee.
hero member
Activity: 629
Merit: 501
Experientia docet
November 23, 2016, 06:42:44 PM
#6

It doesn't let me there, it says that the input is spent, but it's not, its unconfirmed for 72 hours.

It is.
https://blockchain.info/tx/390a7750e3cde8dea1b5b7f6963c2c222c9b1c7c36128b560ee27ecea1531bde

I doubt that transaction have been there for 72 hours. Fee is 54 satoshi per byte and the input have 40 confirmation and 80 per byte fee. Could be wrong though.

Whatever the case is. It'll be best to let that transaction confirm.

Not that one, the other TXs are the older ones, should I just double spend the other 2 without that one?

3977f189d1533a6519df92ea61aeef792434de939d620f7d11996561e273206e
73535a439f2ad97efa7998923a91bfbe4b11bd9338e048aa989b751a9e170179

?

That hex you posted spends an input from 633d4aa816d1c077375cea57f05f4a92010c3f52a753823989e820ec478d10fe:1 and edc498a5de0de762de2fbdc06758c87f5c893998a63bd4c4301588847421749b:1 .

You got the input transactions wrong.

Edit:
Sorry. I misunderstood. You got the input right. But the first input doesn't have anything to do with those two transactions you posted so it's not needed and it won't get dropped by the network just yet (it'll probably confirm before that).
sr. member
Activity: 714
Merit: 251
November 23, 2016, 06:37:12 PM
#5

It doesn't let me there, it says that the input is spent, but it's not, its unconfirmed for 72 hours.

It is.
https://blockchain.info/tx/390a7750e3cde8dea1b5b7f6963c2c222c9b1c7c36128b560ee27ecea1531bde

I doubt that transaction have been there for 72 hours. Fee is 54 satoshi per byte and the input have 40 confirmation and 80 per byte fee. Could be wrong though.

Whatever the case is. It'll be best to let that transaction confirm.

Not that one, the other TXs are the older ones, should I just double spend the other 2 without that one?

3977f189d1533a6519df92ea61aeef792434de939d620f7d11996561e273206e
73535a439f2ad97efa7998923a91bfbe4b11bd9338e048aa989b751a9e170179

?
hero member
Activity: 629
Merit: 501
Experientia docet
November 23, 2016, 06:28:57 PM
#4

It doesn't let me there, it says that the input is spent, but it's not, its unconfirmed for 72 hours.

It is.
https://blockchain.info/tx/390a7750e3cde8dea1b5b7f6963c2c222c9b1c7c36128b560ee27ecea1531bde

I doubt that transaction have been there for 72 hours. Fee is 54 satoshi per byte and the input have 40 confirmation and 80 per byte fee. Could be wrong though. Actually no, you posted it here 5 hours ago.

Whatever the case is. It'll be best to let that transaction confirm.
sr. member
Activity: 714
Merit: 251
November 23, 2016, 06:10:30 PM
#3

It doesn't let me there, it says that the input is spent, but it's not, its unconfirmed for 72 hours.

Somebody probly has to broadcat it in a Core wallet which I have not installed right now.
full member
Activity: 196
Merit: 101
sr. member
Activity: 714
Merit: 251
November 23, 2016, 06:07:34 PM
#1
The fucking bitcoin network is clogged, my transaction is in limbo for 72+ hours, so I have to double spend my transaction because my fucking wallet doesnt support RBF.

I have created a  double spend TX, but I cant broadcast it because the fucking wallet doesnt let me, so somebody please broadcast it for me:

In Hex

Code:
01000000019b74217484881530c4d43ba69839895c7fc85867c0bd2fde62e70ddea598c4ed0100000069463043022028cdacd58b145db882c478029c27b605237869657a49a4f30062ed3619881b09021f68ee0065f8666673dac1d2482bcb130f6c31d68ac6d687856d158b7d669491012102a68215689362729db9ad56f431235a5d3e76f8695630e98c1d759d0662f77621ffffffff0158d31a00000000001976a91461ba1c4beea5a5ce2c8941f0237b378a124189f188ac00000000


I am so angry right now!
Jump to: