I pay to confirm a transaction faster

[sarakuka]

Hi,

I'm willing to pay a fee to someone who can boost this transaction to confirm faster.

https://blockchain.info/tx/df994f4dce12dc8b83d42da984f3aa5a3418ebc525bb3b3835ff5ad5402ac138

Thanks

[mocacinno]

Hi,

I'm willing to pay a fee to someone who can boost this transaction to confirm faster.

https://blockchain.info/tx/df994f4dce12dc8b83d42da984f3aa5a3418ebc525bb3b3835ff5ad5402ac138

Thanks

This transaction uses an unconfirmed output as input to create a new transaction.
Next to this, the error code i got when pushing your raw, signed, transaction to my node seems to indicate that this transaction is double spending an input that has previously been used in a transaction that is still in my mempool (altough the error i got can also mean other things, so this is not confirmed)...

Here's the raw transaction:

Code:

010000000f66cf8be159843805eac84014b6fb099f177537646ab23f05a27bb36b19eec906f70100006b483045022100f452b376dcaa195c4e7ac1e4a8b271a1cab178e3aa94c82e8e83f568f70b5053022000da3098c837bff508c51b18913a33166ae886045f242044f1bf344ed3ba04100121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff5f64c059b28795a62064869f77bad92023700bdf8ad4de334ddbe67f89853c21e50100006b483045022100dae88c34423d1f3ef9fa4025806287265a290a85462e2677c2a94a94bd65ef8e022042bd4fdc5be3143f16f403123d6fcc2f32af6788d313f3d738ba2ce41b489a500121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffffd71dd144b21d365896ab238850df928ae11b62ca414afe314e846d7a34a8b333f00100006a4730440220095b742024fbd6633a1b43ba0689ea5e0ce37aac402d0593c0e1844d7843999102205105dd39b6acf56fa942353e618824d5f5b0bb264e0bf5ecd1daacda9a99a9110121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff364cef00208d92bd23dffd6efcb769a4e22d68ec8c917fdea518e4a8e77a6335e50100006b483045022100c6349c0c365bf2c8ff4123b94ecd079a618e09fba497b8215862434a4576402b02203c32b2a6a876f50d46b739abad1f5f2f288185fb0858718155ce7200a261fc4e0121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff3a9c529dfa1928899e3b795458cd267f4e75219f3ca451adcbf7559f63b72a4ee40100006b483045022100d30da10ba34d0e8087a01c69130270b047739a479337aa6d276ea8586730cfb002202c8985a1337835737f0f3ce9a90c28f02ed821a2c043689ee8eea0b11dac68050121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff239549ad5fca690a4bf52836fc0027fecb50f9c8543fbf39357acd3a66b22371e80100006a4730440220012179ed5896a6b91b65e2a1e53c2861348066c38baeae154bf5a1f5e2fedc7002206de3a831aedd02a63e59b755243226d3868a528ce0b017265a05527c8d0cb3580121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffffb359ac6ebaeb612a85cf260dab284f9bfe4b5c3220f6f574d1fe92eb0039b886e60100006a47304402200caf5d3ce3c7235f8a822895a3036ad1550e465775f8105cb4d05d639f6bea0f022020875ba8ebf3c773ed9974a858c6b3f13032a5bb072bed77eb7c088970f817670121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff5497ada71cce97849c3182227e282e361fe83de9906b55c9fa3410a33204bb86e50100006a47304402200e905ca9ae0152f682d45dc0042b2104f7619e54920e5f96d80787daf1516f0d02206a2da6eccd9fc8c684153d65ab25af87c5b4bf145f334d37376cc191208de9640121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff9125867b987726f01a09299d05d1bf910cf6cd2fc93e16837021eb5098121d88de0100006b4830450221008b58a02095a3a2975ac445f3d329793879681599380536bc5dae38c7ab4341d10220484807ca7ad587d93320a62e94022197d42a9e3ea8aef39c076568871413dd3e0121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffffff7c13fb6f4a041d9700b4cc8e74d8819d6956dbf12168f8bd57fe206306ceab010000006b483045022100bd9dc6d18334b0f7da8ae5dc76a4215d154af0f6f0340a1e6baf6b54ff53794002203ae44b2d4a51a22090052a03db9a7e26bf88c120d89d5489821a827b1f71dbb0012102fee1908dd4a6f15f4e30f55c0f7dcf890f69d42f0fc57c6f1581a9a3d4e80e90ffffffff32fd3feab5ed0550a8691179d0f6fc1bb0870768bffb951d50700b2385eaedaeea0100006a47304402206950221e59f0888effdad357528180bf89a66c0ae10ee6f4bfa5841429db865e02207e65b0b60b04f0ed3eb09060ddf6a99f73008ab9e18f6ab69e6b8bf7a667144c0121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84fffffffff4efe5c1e8a90ad90188b9f90088807426eb79d066b061f38ca284d1b1b0b4d5e20100006a4730440220361c406f56380a5ff170991f7a70a842e93ed2ebf0c0c200a1ac32b4ceb751050220654f2a649a1f6cf9f6a64aac4070257df5048559878abfc1657b90c772f838c50121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff756f59e418c29304ae53e4f28ded6cd3ce0f59e4ff1d9dbd5f443cfbf2fb17dce20100006a473044022003052216322fc547f68a3092e9889bac78a55d38b4d83d4c37a22266c5ee499902200d1d24e5cb8b5d36af798a3caf2f1a65295fae2aecb19237ba9757fa3b9120f90121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffffdbb6313c092f5e0b602a57f8e5c26ed981fa85c2ebf4491d757b701a929a22e4e60100006b483045022100a7ebe09f1011ab79c47c7e04c90db3f62518c0083a74916e8384e61c6a0d0e05022035e6eaf4571e669a347b26671081bb64e6d0629e1995029cd7b13c28bd32ac280121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff224b4e807e2afb155b2d5cd1c033f69888ea2cc69a3c434f277b2c6a0cdb71fedc0100006b483045022100a798f307eecc8442b08be95f77fa59dbb258bafa5c2128d08f636b590d04ddf30220497b027538b8f2af219ef2e3f7a88d3d5c47fdb830ded9731ac557882b9f35500121020640912e1b41abda2b676e604310e0966186dfc76e782b007a619544bf57cb84ffffffff0203be1400000000001976a914b2fe69a2ec1c714f8fe5871ec8861c73c0920efd88ac70b3d201000000001976a91407b68761a72a0b8086cb887a3de2d766352d068088ac00000000

As soon as the conflicting transaction is dropped from my mempool, you can use my wizard to push the new tx to my node: http://www.mocacinno.com/page/txpusher . This way, your transaction will be re-broadcasted trough the network.

You can try to follow this link: http://www.mocacinno.com/feecheck.php?txid=df994f4dce12dc8b83d42da984f3aa5a3418ebc525bb3b3835ff5ad5402ac138#asking in order to find a pool that can potentially include your tx in the block they're working on, but they'd have to include the transaction this tx depends on aswell, and they'd have to drop the conflicting tx from their mempool before pushing this tx to their node...

[paul gatt]

I will do this for you, an easy job, and a lot of people know the way to do it, so I'll do it for free, whenever you need it. Support here, and you do not need to pay any fees. Money is not the most important thing, help is always needed with good people.

[mocacinno]

I will do this for you, an easy job, and a lot of people know the way to do it, so I'll do it for free, whenever you need it. Support here, and you do not need to pay any fees. Money is not the most important thing, help is always needed with good people.

If you're thinking about viabtc: i don't think it'll work, since i suspect the transaction is using inputs that were previously used in a different transaction that remained unconfirmed and is since dropped from the blockchain.info's node mempool....
However, viabtc, like my own node, has modified mempool retention times... So they won't drop a transaction after 3 days, so they'll reject transactions that double spends an input for a longer time...

[paul gatt]

I will do this for you, an easy job, and a lot of people know the way to do it, so I'll do it for free, whenever you need it. Support here, and you do not need to pay any fees. Money is not the most important thing, help is always needed with good people.

If you're thinking about viabtc: i don't think it'll work, since i suspect the transaction is using inputs that were previously used in a different transaction that remained unconfirmed and is since dropped from the blockchain.info's node mempool....
However, viabtc, like my own node, has modified mempool retention times... So they won't drop a transaction after 3 days, so they'll reject transactions that double spends an input for a longer time...

It was bad, I was struggling to find a way to solve this, I thought I had done something wrong, however, when rereading the comment, I realized my mistake, and I thought That this transaction can not fix, or maybe, i'm not the person doing that, really sorry.

[nahtnam]

Is this even possible? I thought transactions were grouped together into blocks so you cant confirm a single transaction.

[mocacinno]

Is this even possible? I thought transactions were grouped together into blocks so you cant confirm a single transaction.

This is true... It's a miner's job to create a block using unconfirmed (verified) transaction it has in it's mempool. The miner then starts hashing the block header (which contains, amongst other things, the merkle root hash of these transactions and a random ellement). If the miner finds a sha256d hash under a certain value (target), he is allowed to broadcast the block to the nodes he is connected to. This is the only way to include a transaction into the blockchain (aka confirm it).

So, to answer your question: if you're not a miner, there is no way to confirm a single transaction. My advice is always pointed towards 3 possible sollutions:
1) create a new transaction, either a RBF, a double spend, a CPFP. This new transaction should be made in such a way it gives the miners an incentive to "unstick" a stuck transaction
2) contacting a miner, ask him to include the transaction in question into the block he/she is currently mining (this is what the viabtc txaccellerator does)
3) wait untill the network either drops the tx, or confirms it (in the end)

[sarakuka]

I don't know what's happening I even paid a higher fee so this transaction will go faster but 0 confirmations.

I also got PM from some members that they would push this transaction but still the same nothing is happening.

Any idea what should I do!

[NeuroticFish]

One of the inputs for your transaction comes from 86b83900eb92fed174f5f620325c4bfe9b4f28ab0d26cf852a61ebba6eac59b3
That's a big transaction, 25kb with zero fee. And you need that one to get confirmed in order to have yours confirmed.

Accelerating that will not work with ViaBTC since the fee is zero. I don't know how CPFP could work for such a big transaction with so many outputs...
However, the problem is not your transaction; the problem is the source of your money (well, one of the sources).

[sarakuka]

I see that is the transaction that is coming from kano.is to my blockchain wallet. I don't understand why it did use that transaction when I had others confirmed and I had more money on wallet.

Seems I'll have to wait that transaction gets confirmed first.

Thanks for your support I really appreciate it.

[mocacinno]

One of the inputs for your transaction comes from 86b83900eb92fed174f5f620325c4bfe9b4f28ab0d26cf852a61ebba6eac59b3
That's a big transaction, 25kb with zero fee. And you need that one to get confirmed in order to have yours confirmed.

Accelerating that will not work with ViaBTC since the fee is zero. I don't know how CPFP could work for such a big transaction with so many outputs...
However, the problem is not your transaction; the problem is the source of your money (well, one of the sources).

I didn't dig this deep, but this is also a good explanation why the OP's tx is not broadcasted properly... If one of the inputs is unconfirmed and comes from a tx that has a 0 fee, it was probably rejected by a large part of the network, so the output never made it to the UTXO set, so OP's tx used inputs that were not in the UTXO, so it got rejected aswell... I tought it had something to do with double spending transactions that were still in the mempool, but this theory might actually be a better one ... I have to dig a bit deeper next time i give some advice  

@OP: if this is true, chances are slim the parent transaction (the zero fee one) will actually get confirmed, unless there's a pool that mines it because it has a high priority (small chance, since most miners don't seem to reserve any more space for high priority transactions).
I'd focus on transaction 86b83900eb92fed174f5f620325c4bfe9b4f28ab0d26cf852a61ebba6eac59b3 first... If it's really important you can spend this output, try to do a CPFP, try to contact Quickseller or macbook-air and offer a reward, or try to convince the sender to double spend the inputs for this transaction to create a new transaction with the same outputs but a higher fee (so less output to the change address).

If you don't really need to spend the output from the parent transaction at this specific time, an other option would be to re-create your transaction, using the same inputs, exept the input you got from tx 86b83900eb92fed174f5f620325c4bfe9b4f28ab0d26cf852a61ebba6eac59b3.

[nahtnam]

Is this even possible? I thought transactions were grouped together into blocks so you cant confirm a single transaction.

This is true... It's a miner's job to create a block using unconfirmed (verified) transaction it has in it's mempool. The miner then starts hashing the block header (which contains, amongst other things, the merkle root hash of these transactions and a random ellement). If the miner finds a sha256d hash under a certain value (target), he is allowed to broadcast the block to the nodes he is connected to. This is the only way to include a transaction into the blockchain (aka confirm it).

So, to answer your question: if you're not a miner, there is no way to confirm a single transaction. My advice is always pointed towards 3 possible sollutions:
1) create a new transaction, either a RBF, a double spend, a CPFP. This new transaction should be made in such a way it gives the miners an incentive to "unstick" a stuck transaction
2) contacting a miner, ask him to include the transaction in question into the block he/she is currently mining (this is what the viabtc txaccellerator does)
3) wait untill the network either drops the tx, or confirms it (in the end)

1. Seems like an interesting way to get it confirmed
2. Seems kinda stupid since you dont know whos gonna successfully mine the block, right?
3. Takes forever.

[mocacinno]

Is this even possible? I thought transactions were grouped together into blocks so you cant confirm a single transaction.

This is true... It's a miner's job to create a block using unconfirmed (verified) transaction it has in it's mempool. The miner then starts hashing the block header (which contains, amongst other things, the merkle root hash of these transactions and a random ellement). If the miner finds a sha256d hash under a certain value (target), he is allowed to broadcast the block to the nodes he is connected to. This is the only way to include a transaction into the blockchain (aka confirm it).

So, to answer your question: if you're not a miner, there is no way to confirm a single transaction. My advice is always pointed towards 3 possible sollutions:
1) create a new transaction, either a RBF, a double spend, a CPFP. This new transaction should be made in such a way it gives the miners an incentive to "unstick" a stuck transaction
2) contacting a miner, ask him to include the transaction in question into the block he/she is currently mining (this is what the viabtc txaccellerator does)
3) wait untill the network either drops the tx, or confirms it (in the end)

1. Seems like an interesting way to get it confirmed
2. Seems kinda stupid since you dont know whos gonna successfully mine the block, right?
3. Takes forever.

Well, the second options isn't as stupid as it sounds. Quickseller and macbook-air can push transactions in f2pool blocks.
As you can see here: https://blockchain.info/nl/blocks/F2Pool F2pool mines more than 10 blocks/day on avarage... So the time between 2 blocks is usually less than 3 hours (on avarage). So when you give a bounty to Quickseller or macbook-air (and they accept this bounty), you can usually say that your transaction will be confirmed in less than 3 hours (on average).

ViaBTC doesn't need a bounty, they just use an online form, they used to mine less blocks (on average) compared to f2pool, but looking at https://blockchain.info/nl/blocks/ViaBTC it looks like they added more hashrate, since they also seem to mine 10+ blocks/day nowadays.

So, if you give a small bounty to either Quickseller or macbook-air AND you use the ViaBTC txaccelerator, and you pay btc.com (they also have a paying accelerator), you can allmost be sure that your tx will be confirmed in ~1hour. Offcourse, you'll have payed way more than if you added sufficient fees when creating a transaction in the first place

The thirth option (waiting untill most nodes drop the tx from the mempool isn't that stupid either. The default node's setting is to drop a transaction from it's mempool if it remains unconfirmed for 72 hours. Some nodes (like mine) have edited this setting (i keep a transaction for 10 days), but if you wait 4-5 days, chances are good that your transaction will have been forgotten by enough nodes, so you can safely re-use the unspent outputs to create a new transaction.

[salmanahmedone]

Hi,

I'm willing to pay a fee to someone who can boost this transaction to confirm faster.

https://blockchain.info/tx/df994f4dce12dc8b83d42da984f3aa5a3418ebc525bb3b3835ff5ad5402ac138

Thanks

Well i can suggest you a free way to speed up your transaction. Just accelerate the Transaction by viabtc.com Just put the transaction ID and click submit, it will be automatically speed up.

EDIT: By the way that transaction is already been confirmed 

[nahtnam]

Is this even possible? I thought transactions were grouped together into blocks so you cant confirm a single transaction.

This is true... It's a miner's job to create a block using unconfirmed (verified) transaction it has in it's mempool. The miner then starts hashing the block header (which contains, amongst other things, the merkle root hash of these transactions and a random ellement). If the miner finds a sha256d hash under a certain value (target), he is allowed to broadcast the block to the nodes he is connected to. This is the only way to include a transaction into the blockchain (aka confirm it).

So, to answer your question: if you're not a miner, there is no way to confirm a single transaction. My advice is always pointed towards 3 possible sollutions:
1) create a new transaction, either a RBF, a double spend, a CPFP. This new transaction should be made in such a way it gives the miners an incentive to "unstick" a stuck transaction
2) contacting a miner, ask him to include the transaction in question into the block he/she is currently mining (this is what the viabtc txaccellerator does)
3) wait untill the network either drops the tx, or confirms it (in the end)

1. Seems like an interesting way to get it confirmed
2. Seems kinda stupid since you dont know whos gonna successfully mine the block, right?
3. Takes forever.

Well, the second options isn't as stupid as it sounds. Quickseller and macbook-air can push transactions in f2pool blocks.
As you can see here: https://blockchain.info/nl/blocks/F2Pool F2pool mines more than 10 blocks/day on avarage... So the time between 2 blocks is usually less than 3 hours (on avarage). So when you give a bounty to Quickseller or macbook-air (and they accept this bounty), you can usually say that your transaction will be confirmed in less than 3 hours (on average).

ViaBTC doesn't need a bounty, they just use an online form, they used to mine less blocks (on average) compared to f2pool, but looking at https://blockchain.info/nl/blocks/ViaBTC it looks like they added more hashrate, since they also seem to mine 10+ blocks/day nowadays.

So, if you give a small bounty to either Quickseller or macbook-air AND you use the ViaBTC txaccelerator, and you pay btc.com (they also have a paying accelerator), you can allmost be sure that your tx will be confirmed in ~1hour. Offcourse, you'll have payed way more than if you added sufficient fees when creating a transaction in the first place

The thirth option (waiting untill most nodes drop the tx from the mempool isn't that stupid either. The default node's setting is to drop a transaction from it's mempool if it remains unconfirmed for 72 hours. Some nodes (like mine) have edited this setting (i keep a transaction for 10 days), but if you wait 4-5 days, chances are good that your transaction will have been forgotten by enough nodes, so you can safely re-use the unspent outputs to create a new transaction.

Oh I see. Still in the end, the best option is to just add a few extra btc in the fee, right?

[mocacinno]

Oh I see. Still in the end, the best option is to just add a few extra btc in the fee, right?

yes,
if you pick a sub-standard fee, you're relying either on chance or you're paying a premium afterwards. Not to mention the time and efford you'd have to spend, and the frustration of seeing an unconfirmed transaction 

Personally, i pick low fees when transferring between my own wallets, and a higher fee when i'm sending to somebody else, especially when i'm paying for good or services.

[paul gatt]

Oh I see. Still in the end, the best option is to just add a few extra btc in the fee, right?

yes,
if you pick a sub-standard fee, you're relying either on chance or you're paying a premium afterwards. Not to mention the time and efford you'd have to spend, and the frustration of seeing an unconfirmed transaction 

Personally, i pick low fees when transferring between my own wallets, and a higher fee when i'm sending to somebody else, especially when i'm paying for good or services.

I appreciate your doing, it represents a smart person. If he knows to use a reasonable fee, I'm sure he will not have this problem. I usually pay 0.002 for transactions greater than 0.2 btc, and I've never had a problem with it.