https://blockchain.info/en/tx/d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
Topic: transaction disappeared from block chain?? (Read 820 times)
your transaction was confirmed
https://blockchain.info/en/tx/d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
https://blockchain.info/en/tx/d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
Hmm, again, from that wiki page:
I know, that is talking about the reference client's block construction behavior but it might explain a few things if it is a fair representation of what miners are doing.
A quick scan of my mempool of unconfirmed transactions and their priority, sorted by "highest priority":
First column is bytes. That's pretty much going to eat up the "30000 is reserved for highest priority" for quite some time. You're currently ranked #171 from the top of that list. There's 577781 bytes of "high priority" traffic ahead of yours.
Because your tx is fee free, it won't fit in the second group.
It is unclear how many pools use the transaction selection models that the reference client uses, or what quirks they have.
This is going to take a while. Be extremely careful if you're thinking of resending, it could still confirm.
Quote
Including in Blocks
This section describes how the reference implementation selects which transactions to put into new blocks, with default settings. All of the settings may be changed if a miner wants to create larger or smaller blocks containing more or fewer free transactions.
30,000 bytes in the block are set aside for the highest-priority transactions, regardless of transaction fee. Transactions are added highest-priority-first to this section of the block.
Then transactions that pay a fee of at least 0.0001 BTC/kb are added to the block, highest-fee transactions first, until the block is not more than 300,000 bytes big.
The remaining transactions remain in the miner's "memory pool", and may be included in later blocks if their priority or fee is large enough.
This section describes how the reference implementation selects which transactions to put into new blocks, with default settings. All of the settings may be changed if a miner wants to create larger or smaller blocks containing more or fewer free transactions.
30,000 bytes in the block are set aside for the highest-priority transactions, regardless of transaction fee. Transactions are added highest-priority-first to this section of the block.
Then transactions that pay a fee of at least 0.0001 BTC/kb are added to the block, highest-fee transactions first, until the block is not more than 300,000 bytes big.
The remaining transactions remain in the miner's "memory pool", and may be included in later blocks if their priority or fee is large enough.
I know, that is talking about the reference client's block construction behavior but it might explain a few things if it is a fair representation of what miners are doing.
A quick scan of my mempool of unconfirmed transactions and their priority, sorted by "highest priority":
Code:
22247 29510957894.26107407
22251 24617855466.11368179
22237 23797564629.60096359
22245 23794448299.07243729
27302 21127378315.33507919
22238 21059217907.33554459
22229 18540419334.94335556
22254 16502444715.59822273
22237 16130040247.36238289
22251 15074281814.33272171
22249 15068602923.64821625
22240 12768199194.55590630
5965 10029852114.08262253
7176 8947361947.19983292
2852 7769685225.87504864
22240 7673617191.58819962
4332 7591994500.56230640
5693 7554179627.29180527
22241 7394041900.16759014
9256 7123151255.12517929
5559 6836646125.44707775
259 6533343333.33333302
6436 6173324479.56040573
523 6033913454.75903320
1261 5822628219.26124096
16646 5444277224.78949356
258 5092818188.14678001
....
Because your tx is fee free, it won't fit in the second group.
It is unclear how many pools use the transaction selection models that the reference client uses, or what quirks they have.
This is going to take a while. Be extremely careful if you're thinking of resending, it could still confirm.
First of all, there are several key components in play here.
1) Your wallet. It has an unconfirmed transaction in it. Your bitcoin client will keep doing a ResendWalletTransactions() every so often to the P2P network until it is either confirmed by a miner, or you delete it from the wallet.
2) The P2P network. Every bitcoin node keeps a list of unconfirmed transactions in memory (the MemPool) so that they can be relayed to other nodes. They time out after a while - exactly how long depends on local factors, activity, node restarts etc. When the nodes see transactions appear in blocks, they also get removed from the mempool.
3) Miners. They take the highest priority transactions from the mempool and set them in stone in blocks.
Wallet clients normally resend the transaction periodically.
I poked around a bit. *my* clients all know about the transaction of yours:
It looks like you spent 5 outputs:
#1570 of 7bd8cecc8481baffbb545efc6f9949ccd2c3d87241ff6316c2d4fb975d055891 (0.109 btc 2071 confirm)
#836 of 330a32b6d7312ea2ad8b6b50cb6e418d251d73822aa3d48c979aea9f0544658f (0.161 2226 confirm)
#908 of ba8a17326f7f85ca27e2be8954d8da4ac8755486ce8f71b463f86da73c44b455 (0.021 btc 801 confirm)
#540 of 19c53d50895e35d1a0445c66dca1bef3cde39dd64603f1729a4db8c6dff6174b (0.024 btc 1762 confirm)
#2722 of d07d6c039b95484a634ea5d8e3e44da54aed8abcb8d313da92396a8e62e3a758 (0.093 btc 1327 confirm)
My quick dig around in the blockchain shows these as unspent.
However, on https://en.bitcoin.it/wiki/Transaction_fees it talks about transaction priority as a prerequisite for a fee-free transaction. I'm pretty sure that is old information.
.. so it should qualify for fee-free. In my client's mempool, is ranked at priority 2014 of 2180.. right near the top.
Aside from the zero fee (which it is entitled to be, according to the rules), I'm not sure I see why this hasn't confirmed yet.
What am I missing?
1) Your wallet. It has an unconfirmed transaction in it. Your bitcoin client will keep doing a ResendWalletTransactions() every so often to the P2P network until it is either confirmed by a miner, or you delete it from the wallet.
2) The P2P network. Every bitcoin node keeps a list of unconfirmed transactions in memory (the MemPool) so that they can be relayed to other nodes. They time out after a while - exactly how long depends on local factors, activity, node restarts etc. When the nodes see transactions appear in blocks, they also get removed from the mempool.
3) Miners. They take the highest priority transactions from the mempool and set them in stone in blocks.
Wallet clients normally resend the transaction periodically.
I poked around a bit. *my* clients all know about the transaction of yours:
Code:
$ bitcoin-cli getrawtransaction "d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563" 1
...
"vout" : [
{
"value" : 0.40000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 0910bf8deaccae0abb0a201107ab57fccba85e3f OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a9140910bf8deaccae0abb0a201107ab57fccba85e3f88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"1pw9R8BCWdojic8bryNqaAXoh77D5tBeb"
]
}
},
It looks like you spent 5 outputs:
#1570 of 7bd8cecc8481baffbb545efc6f9949ccd2c3d87241ff6316c2d4fb975d055891 (0.109 btc 2071 confirm)
#836 of 330a32b6d7312ea2ad8b6b50cb6e418d251d73822aa3d48c979aea9f0544658f (0.161 2226 confirm)
#908 of ba8a17326f7f85ca27e2be8954d8da4ac8755486ce8f71b463f86da73c44b455 (0.021 btc 801 confirm)
#540 of 19c53d50895e35d1a0445c66dca1bef3cde39dd64603f1729a4db8c6dff6174b (0.024 btc 1762 confirm)
#2722 of d07d6c039b95484a634ea5d8e3e44da54aed8abcb8d313da92396a8e62e3a758 (0.093 btc 1327 confirm)
My quick dig around in the blockchain shows these as unspent.
However, on https://en.bitcoin.it/wiki/Transaction_fees it talks about transaction priority as a prerequisite for a fee-free transaction. I'm pretty sure that is old information.
Code:
$ bitcoin-cli getrawmempool true
...
"d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563" : {
"size" : 819,
"fee" : 0.00000000,
"time" : 1394515894,
"height" : 289982,
"startingpriority" : 687882974.94871795,
"currentpriority" : 716569858.93772888,
"depends" : [
]
},
Aside from the zero fee (which it is entitled to be, according to the rules), I'm not sure I see why this hasn't confirmed yet.
What am I missing?
Thanks for the explaination/info. JoelKatz said they never left my wallet, but fsb4000 said it's still on the network. So now this raises even more questions: on what premise does blockchain.info have on choosing whether to delete a transaction data or not? Since it's still actually on the p2p network, does that mean I just have to wait until it gets confirmed?
It's just blockchain.info deleted the transaction from the site. The transaction is still in Bitcoin p2p network.
For example, the transaction d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563 exists in my Bitcoin QT mempool
and here:
http://blockr.io/zerotx/info/d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
blockchain.info =/= bitcoin p2p network
For example, the transaction d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563 exists in my Bitcoin QT mempool
and here:
http://blockr.io/zerotx/info/d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
blockchain.info =/= bitcoin p2p network
The short version: Your Wallet thinks the transaction has been spent. It'll try to re-broadcast it to the network periodically.
If you're using older bitcoin software, check out pywallet - you can delete the transaction and stop your client trying to re-send the transaction. This will free up the 0.4 btc for respending.
If you are using 0.9rc2 or later, there are new options:
-rescan Rescan the block chain for missing wallet transactions
-zapwallettxes Clear list of wallet transactions (diagnostic tool; implies -rescan)
The latter discards the transaction record and rescans the wallet to find them again. This gets rid of stuck / unconfirmed transactions that can't be confirmed.
Note: if the network has a copy of the transaction in the P2P network and its queued up at a miner, it could still be confirmed - in which case your client will notice and update the balances.
No matter what you do (pywallet or a 0.9 zap/rescan), a solid backup of your wallet would be in order.
If you're using older bitcoin software, check out pywallet - you can delete the transaction and stop your client trying to re-send the transaction. This will free up the 0.4 btc for respending.
If you are using 0.9rc2 or later, there are new options:
-rescan Rescan the block chain for missing wallet transactions
-zapwallettxes Clear list of wallet transactions (diagnostic tool; implies -rescan)
The latter discards the transaction record and rescans the wallet to find them again. This gets rid of stuck / unconfirmed transactions that can't be confirmed.
Note: if the network has a copy of the transaction in the P2P network and its queued up at a miner, it could still be confirmed - in which case your client will notice and update the balances.
No matter what you do (pywallet or a 0.9 zap/rescan), a solid backup of your wallet would be in order.
I sent 0.4 btc and forgot to pay the fee. This transaction was unconfirmed for several days, but was on the blockchain and status said priority was high during these several days. Now, it just totally disappeared. I was thinking it was not included in any new blocks, no problem, I'll just send it again and pay the fee.
However, this 0.4 btc never went back to my wallet, never made it to the other wallet, and does not show on the blockchain. It's in limbo somewhere. Where is it, and how can I get it back? Original thread HERE.
Transaction ID: d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
wallet it's suppose to go to: https://blockchain.info/address/1pw9R8BCWdojic8bryNqaAXoh77D5tBeb
However, this 0.4 btc never went back to my wallet, never made it to the other wallet, and does not show on the blockchain. It's in limbo somewhere. Where is it, and how can I get it back? Original thread HERE.
Transaction ID: d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
wallet it's suppose to go to: https://blockchain.info/address/1pw9R8BCWdojic8bryNqaAXoh77D5tBeb
Please call that service "blockchain.info". "Transaction disappeared from block chain" would be interpreted as a major re-org of the blockchain or a major flaw in bitcoin
However, this 0.4 btc never went back to my wallet, never made it to the other wallet, and does not show on the blockchain. It's in limbo somewhere. Where is it, and how can I get it back?
It never left your wallet. It's still exactly where it was all along.
You may have to do a rescan on bitcoinqt
I sent 0.4 btc and forgot to pay the fee. This transaction was unconfirmed for several days, but was on the blockchain and status said priority was high during these several days. Now, it just totally disappeared. I was thinking it was not included in any new blocks, no problem, I'll just send it again and pay the fee.
However, this 0.4 btc never went back to my wallet, never made it to the other wallet, and does not show on the blockchain. It's in limbo somewhere. Where is it, and how can I get it back? Original thread HERE.
Transaction ID: d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
wallet it's suppose to go to: https://blockchain.info/address/1pw9R8BCWdojic8bryNqaAXoh77D5tBeb
However, this 0.4 btc never went back to my wallet, never made it to the other wallet, and does not show on the blockchain. It's in limbo somewhere. Where is it, and how can I get it back? Original thread HERE.
Transaction ID: d2d79b1c5153c8e6c4dc007044b277b345a4867954cd8d9ec5d5b9f0675a0563
wallet it's suppose to go to: https://blockchain.info/address/1pw9R8BCWdojic8bryNqaAXoh77D5tBeb
Jump to: