Author

Topic: A transaction has 0 priority (Read 651 times)

copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
March 01, 2016, 08:47:41 AM
#12
Too bad... So, as far as I've understood, in the worst case I could wait until the priority of my first transaction becomes something like 57,000,000? It's 6,500,000 now and is growing about 2,000,000 per day...
https://www.blocktrail.com/BTC/tx/d902bc7ecc0d236aafed14ef509be63cd2e357ab6a7f8c2a2d7d4f343ecf3e81

Sounds about right. My estimate[1] is 17.9 days for enough priority of the input.

[1] 144 confirmations for 1 BTC or 144*20 for 0.05
2880 confirmations minus the 291 the input already has = 2589
2589 / 6 = 431 hours or 17.9 days
copper member
Activity: 924
Merit: 1007
hee-ho.
March 01, 2016, 08:43:59 AM
#11
Too bad... So, as far as I've understood, in the worst case I could wait until the priority of my first transaction becomes something like 57,000,000? It's 6,500,000 now and is growing about 2,000,000 per day...
https://www.blocktrail.com/BTC/tx/d902bc7ecc0d236aafed14ef509be63cd2e357ab6a7f8c2a2d7d4f343ecf3e81

 Can you explain a bit what you meant by priority of 57,000,000...

transactions with priority over 57,600,000 are free. that means no fee required. though in real practice it may still take time to confirm.
newbie
Activity: 32
Merit: 0
March 01, 2016, 08:34:37 AM
#10
Too bad... So, as far as I've understood, in the worst case I could wait until the priority of my first transaction becomes something like 57,000,000? It's 6,500,000 now and is growing about 2,000,000 per day...
https://www.blocktrail.com/BTC/tx/d902bc7ecc0d236aafed14ef509be63cd2e357ab6a7f8c2a2d7d4f343ecf3e81

 Can you explain a bit what you meant by priority of 57,000,000...
newbie
Activity: 34
Merit: 0
March 01, 2016, 07:54:03 AM
#9
Too bad... So, as far as I've understood, in the worst case I could wait until the priority of my first transaction becomes something like 57,000,000? It's 6,500,000 now and is growing about 2,000,000 per day...
https://www.blocktrail.com/BTC/tx/d902bc7ecc0d236aafed14ef509be63cd2e357ab6a7f8c2a2d7d4f343ecf3e81
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
March 01, 2016, 06:09:22 AM
#8
Chaining transactions after each other makes no sense. The idea behind this is "CPFP" (child pays for parent), but this is not commonly implemented by miners.
newbie
Activity: 34
Merit: 0
March 01, 2016, 01:40:57 AM
#7
Ooookay... I did another transaction with the unspent change, here:
https://www.blocktrail.com/BTC/tx/08841ee404520a01754a30ae4ecc00f0309d64c4786d68eae346001559d8cd9e
Total Inputs   0.00163960 BTC
Total Outputs   0.00150000 BTC
Fee   0.00013960 BTC
Size   486 bytes

The fee looks high enough, and blockchain.info indicates it will be processed "Very soon":
https://blockchain.info/en/tx/08841ee404520a01754a30ae4ecc00f0309d64c4786d68eae346001559d8cd9e

However, it's still not confirmed after about 10 hours...

Quote
As for what you've tried to do, your first transaction needs to confirm first. If I understood correctly this shouldn't speed anything up, but I'm not sure I did.
As it was explained to some other guy, the miners will want to include the second transaction, because it has a high fee. But they won't be able to include it until the first one is included, so they will want to include the first one faster, too.
legendary
Activity: 2968
Merit: 3406
Crypto Swap Exchange
February 29, 2016, 09:30:13 PM
#6
Everything you did was wrong base on the fee used. On your first transaction: https://blockchain.info/tx/d902bc7ecc0d236aafed14ef509be63cd2e357ab6a7f8c2a2d7d4f343ecf3e81 Your fee was only 0.0000113 BTC and what you saw to send with higher fee is right but again you did the wrong thing twice (by sending less fee than recommended): https://blockchain.info/tx/b6d9ad8d516e73ecb88743b75edcd39dee30994caf44e278572ac3f0bb199eb9 Your fee was only 0.00004534 BTC

First transaction fee needed as ideal and fast confirmation: 0.00013500
Second transaction fee needed as ideal and fast confirmation: 0.00013560
Normal standard fee for confirmations: 0.0001
Around 60 Satoshi per byte would be ideal
legendary
Activity: 1078
Merit: 1024
February 29, 2016, 06:12:26 PM
#5
Usually the best strategy is to wait for confirmation if you messed something up.
To avoid messing something up or reducing your confirmation time, you should do the following.

1. Avoid using unconfirmed funds.
2. Decent tx fee.
3. Use a wallet that isn't garbage at managing inputs.

As for what you've tried to do, your first transaction needs to confirm first. If I understood correctly this shouldn't speed anything up, but I'm not sure I did.
copper member
Activity: 924
Merit: 1007
hee-ho.
February 29, 2016, 04:09:04 PM
#4
no idea (anyone knows?).
but even if they should help speed things up your tx have a fairly low fee and dust output.
newbie
Activity: 34
Merit: 0
February 29, 2016, 03:35:19 PM
#3
Okay... I'll try to explain in more detail... basically, I made another transaction earlier:
https://www.blocktrail.com/BTC/tx/d902bc7ecc0d236aafed14ef509be63cd2e357ab6a7f8c2a2d7d4f343ecf3e81
and it's still unconfirmed, so I googled a little and saw someone advised to make another transaction using the unspent change, with a higher fee, so it will look more attractive for miners to include in the next block, but they won't be able to include it without including the first one. And so I sent another transaction (the one in my first post), basically I sent it to myself... so now I don't even know if I did the right thing... will it actually speed up the confirmation process?
copper member
Activity: 924
Merit: 1007
hee-ho.
February 29, 2016, 03:30:49 PM
#2
of course it have 0 priority. the input is zero confirmation old (unconfirmed). happens to a lot of people.
newbie
Activity: 34
Merit: 0
February 29, 2016, 03:18:53 PM
#1
Hello everyone, tried to google for my problem, but couldn't find it, apparently I'm the first one who had it. I made a transaction, and its priority is shown as 0 (zero) and it's staying zero, it's not increasing:
https://www.blocktrail.com/BTC/tx/b6d9ad8d516e73ecb88743b75edcd39dee30994caf44e278572ac3f0bb199eb9
Now how the hell is this even possible? And what should I do with it?  Huh
Jump to: