Bitcoin Forum
July 06, 2024, 08:08:16 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: What's wrong with my bitcoin  (Read 670 times)
ahqahq123 (OP)
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
April 27, 2016, 04:37:30 PM
 #1

I send 0.15 bitocin via bitcoin core 72 hours ago, but still unconfirmed now.

TXID : c40c5cbedd21796f14f23ff59b6e14c8cce0d1bdd8c236a7aeda385700ccf174

blockchain show my transaction was rejected yesterday, but today the transaction show on the blockchian again.

what will happen to my bitcoin?

DannyHamilton
Legendary
*
Offline Offline

Activity: 3430
Merit: 4681



View Profile
April 27, 2016, 04:48:51 PM
 #2

That transaction spends an unconfirmed output from transaction 1bfea4383358c8fc95507b9e20169ece99738947764348e3ea2d1102cdad8ad5

Your transaction cannot confirm until that previous transaction confirms. That transaction paid a VERY small transaction fee (only 1 satoshi per byte), and so it may take a VERY long time to confirm (and possibly may never confirm).

If that previous transaction confirms, then there's a pretty good chance that your transaction will confirm.

If that previous transaction never confirms, then your transaction will never confirm.

Do you know anything about transaction 1bfea4383358c8fc95507b9e20169ece99738947764348e3ea2d1102cdad8ad5  ?
Was it the change from 0.000227 BTC that you sent to 1NiDm6QVvtcFJCSXsGQhrrchz9d9ziKmuN or was it 0.00073448 BTC that you received from someone else?
AgentofCoin
Legendary
*
Offline Offline

Activity: 1092
Merit: 1001



View Profile
April 27, 2016, 04:56:14 PM
 #3

I send 0.15 bitocin via bitcoin core 72 hours ago, but still unconfirmed now.
TXID : c40c5cbedd21796f14f23ff59b6e14c8cce0d1bdd8c236a7aeda385700ccf174
blockchain show my transaction was rejected yesterday, but today the transaction show on the blockchian again.

what will happen to my bitcoin?



It seems that your tx is the last part of a chain of four prior doublespends.
The fees are too small on each of them. This will take a very long time, if ever.
This looks like a payout from a gambling site or a ponzi site. Is it?

The original sender keeps broadcasting these txs, which is why it disappeared
and is back again now. Your bitcoin will either stay in limbo here till all others
are confirmed or be returned to sender after some time.




I support a decentralized & unregulatable ledger first, with safe scaling over time.
Request a signed message if you are associating with anyone claiming to be me.
ahqahq123 (OP)
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
April 27, 2016, 05:00:08 PM
 #4

is there any way to solve this problem?

if not, my bitcoin will never stay in the block?
DannyHamilton
Legendary
*
Offline Offline

Activity: 3430
Merit: 4681



View Profile
April 27, 2016, 05:03:44 PM
 #5

is there any way to solve this problem?
Do you know anything about transaction 1bfea4383358c8fc95507b9e20169ece99738947764348e3ea2d1102cdad8ad5  ?
Was it a transaction where you sent 0.000227 BTC to 1NiDm6QVvtcFJCSXsGQhrrchz9d9ziKmuN , or was it 0.00073448 BTC that you received from someone else?

You'll need to know something about that transaction in order to figure out if you can fix the problem, and how.

if not, my bitcoin will never stay in the block?

If you don't get the problem fixed, then the transactions might confirm in the future, or they might never confirm.
ahqahq123 (OP)
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
April 27, 2016, 05:10:07 PM
 #6

Yes , I sent to the 1NiDm6QVvtcFJCSXsGQhrrchz9d9ziKmuN, but what the relationship between the other, and what can I fix this?
DannyHamilton
Legendary
*
Offline Offline

Activity: 3430
Merit: 4681



View Profile
April 27, 2016, 05:19:39 PM
 #7

Yes , I sent to the 1NiDm6QVvtcFJCSXsGQhrrchz9d9ziKmuN

Ok, then there is one more transaction that we'll need to understand...

Did you send 0.000024 BTC to 1Dkb3mqNr543uvW3LhFmYxVcVPW7cKVhzu with transaction 4e28915e2810fb918e493f7e13a50227804c8672683b71443dd18194375d34ed ?

If you did sent this other transaction, then you will be able to fix this whole problem yourself.

but what the relationship between the other, and what can I fix this?

The relationship is that the change from the unconfirmed 0.000227 BTC transaction that you sent 1NiDm6QVvtcFJCSXsGQhrrchz9d9ziKmuN was used to fund the transaction that you are asking about.  The transaction you are asking about will not confirm until this earlier transaction confirms.

You will use -zapwallettxes to fix this, but only if you also sent transactionID 4e28915e2810fb918e493f7e13a50227804c8672683b71443dd18194375d34ed
ahqahq123 (OP)
Newbie
*
Offline Offline

Activity: 15
Merit: 0


View Profile
April 27, 2016, 05:23:04 PM
 #8

what is  -zapwallettxes

how can I  use this to fix, can you tell me the step, plz

thank you very very much
DannyHamilton
Legendary
*
Offline Offline

Activity: 3430
Merit: 4681



View Profile
April 27, 2016, 05:34:50 PM
 #9

what is  -zapwallettxes

how can I  use this to fix, can you tell me the step, plz

thank you very very much

If the version of Bitcoin Core that you are running is older than version 10.0, then upgrade to version 10.0 or higher.

Then shut down Bitcoin Core.

Open a command line window in your operating system.

Run the bitcoin program from the command line adding -zapwallettxes as a command line option

The wallet will purge all three of these transactions, and will re-scan the blockchain to make sure that it isn't missing any confirmed transactions.

When the re-scan is complete, you will have access to the full balance again.  Resend your 3 transactions, but make sure that you set a proper transaction fee this time so the transactions will confirm quickly.  I always use a transaction fee of at least 0.0001 BTC per transaction, and higher if the transaction uses a lot of inputs or sends to a lot of outputs.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!