Set Decent Fee, 2 Hours Later 0 Confirmations

[ownageplocks]

transaction shows here as unconfirmed:

https://blockchain.info/tx/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

How do I check if it has an unconfirmed input?

Paste the TX on this site : http://btc.blockr.io/

No entry = no mempool = PRIVAT (blockchain.info) mempool and may be never emit on official Bitcoin network.

I understand that, the problem is my wallet isn't on the "private mempool" it's a different wallet. So if it never emits on the BTC network does that mean I'll never receive anything?
And meuh I understand it's not in the mempool, what can I do to change that, you keep stating the same information with no way to resolve it.

[AngryDwarf]

Transaction exists in my mempool:

Code:

21:05:42

getrawtransaction 21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c


21:05:42

0100000002b058379b33359eca1f9b865cc9098dfd77ba7ad62547d51d8c3cd5d53ae30dc5010000006b483045022100ad161fd11dbcb782d77bb6074037a8e4e0de190b54018832de43d6e4a37c0eb902207439715d138b3ebf0e9ab4c32075543af44e903b04d2f278301340ba85dba8e3012103224f9b97750c5ad14119bcc2320ac9812abd093bb42c174a4ccf5ec539c5154fffffffff58b8c7e27b664d95f8be1e9a374500d1ee630a415612b7a21bb7ca8c500f0bf5000000006a4730440220344ce181fdb37e4947f2139790ff919c823b20fb7d779cfc08622329b621fdec02201003a9740e64ab629ce2b893382169c14cee54df1e01902edf9d89d6548f1eaf012103723135689e1d35b0b5ddfd0b38309a26419e676aca3e8066998493366eec43ddffffffff02c323e300000000001976a914e00d29d9fd552bc8cdcb762810e32d504f7d629c88ac64e89301000000001976a914b9025946dbc9181fc9d9d397eb9d564a7abdd94788ac00000000

EDIT: Which means it has been broadcast on the network.

[Meuh6879]

No.

http://btc.blockr.io/tx/info/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

[AngryDwarf]

No.

http://btc.blockr.io/tx/info/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

I don't think that site displays unconfirmed transactions, only confirmed ones. The unconfirmed transaction appears on other block explorer sites.

e.g. https://www.blocktrail.com/BTC/tx/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

and https://bitcoinchain.com/block_explorer/tx/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

[ownageplocks]

No.

http://btc.blockr.io/tx/info/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

I don't think that site displays unconfirmed transactions, only confirmed ones. The unconfirmed transaction appears on other block explorer sites.

e.g. https://www.blocktrail.com/BTC/tx/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

I'm glad we got that cleared up. I was able to accelerate both of my transactions on the accelerator. Hopefully I'll see some confirmations soon.

[AngryDwarf]

I'm glad we got that cleared up. I was able to accelerate both of my transactions on the accelerator. Hopefully I'll see some confirmations soon.

Cool. Did you use the ViaBTC accelerator? If so, you might have to wait for them to find a block (unless another miner decides to include it first).

[Lorilikes]

I am experiencing a similar problem, and the part that most irritates me is I used a bitcoin ATM and their fees were tiny,  and that is bad business.
5 hours later and still zzzzz.

[ownageplocks]

Yeah it is really bad business to send transactions with such low fees. Very frustrating. As long as I get it within 24 hours I suppose I'll be happy. This certainly doesn't feel like the future of money though.
And yes Dwarf that's the accelerator I used.

[lionheart78]

No.

http://btc.blockr.io/tx/info/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

I don't think that site displays unconfirmed transactions, only confirmed ones. The unconfirmed transaction appears on other block explorer sites.

e.g. https://www.blocktrail.com/BTC/tx/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

and https://bitcoinchain.com/block_explorer/tx/21869ca0ea465c77b06768f0414edf94585d69fdde9a25be6dd58cb4820f7a5c

I was also puzzled why that site does not show the transaction stated by OP, since I can see it on blockchain.info and the other two AngryDwarf had stated, seems this is the reason why it does not show the two unconfirmed transaction.  It only records the confirmed one, seems not that reliable to me.

I'm glad we got that cleared up. I was able to accelerate both of my transactions on the accelerator. Hopefully I'll see some confirmations soon.

Cool. Did you use the ViaBTC accelerator? If so, you might have to wait for them to find a block (unless another miner decides to include it first).

I guess he already pushed it and someone before him also pushed the transaction.  Probably the pool does not found a single block yet.

One of the problem with multiple address in the same wallet sending a single transaction is that, the fee was divided by how many addresses were used plus the destination addresses which I think should be fixed.  As a result it is better to use a single isolated address created by private key transfer to make sure we got the minimum possible amount of txfee.

[ownageplocks]

Can anyone give me any sort of estimation of the time this might take to complete one confirmation? It's been 5 hours already

[NeuroticFish]

Yeah it is really bad business to send transactions with such low fees.

Your fee is not low, it's 120 sat/byte. I've sent a transaction with 5 sat/byte Friday and it went thru by Sunday. That one was low fee

Your problem is the bad timing and not looking on the right place. Let me explain:


The image shows clearly how busy the network got .. suddenly. Again.
Before sending a transaction you can look here: https://btc.com/stats/unconfirmed-tx
If the mempool is on the rise, you better set even more than the recommended fee.
If the mempool is cool, then even awfully low fees are okay.

PS. I will try to accelerate your transaction(s) @ ViaBTC.
PS2. Estimation: less than 12h

[AngryDwarf]

Can anyone give me any sort of estimation of the time this might take to complete? It's been 5 hours already

You will have to wait for ViaBTC to find a block, which is pure luck. Last one they found was 4 hours ago. Alternatively, another miner might include the transaction, but traffic seems heavy again at the moment, so higher fee transactions will take priority.

https://blockchain.info/blocks

[ownageplocks]

Yeah it is really bad business to send transactions with such low fees.

Your fee is not low, it's 120 sat/byte. I've sent a transaction with 5 sat/byte Friday and it went thru by Sunday. That one was low fee

Your problem is the bad timing and not looking on the right place. Let me explain:


The image shows clearly how busy the network got .. suddenly. Again.
Before sending a transaction you can look here: https://btc.com/stats/unconfirmed-tx
If the mempool is on the rise, you better set even more than the recommended fee.
If the mempool is cool, then even awfully low fees are okay.

PS. I will try to accelerate your transaction(s) @ ViaBTC.
PS2. Estimation: less than 12h

Thank you neurotic for finally offering me some solid info as to what is going on. I knew the fee wasn't that low...

[Meuh6879]

I don't think that site displays unconfirmed transactions, only confirmed ones.

this site display unconfirmed transactions when they are EMIT ...

others blockexplorers use miners to have a pre-block vision with cheating transactions.
i don't use this blockexplorer for this.

on the site that i have linked, i see the realtime mempool with the original and FORCED rules of the Bitcoin network.

not the cheating privat mempool of a miner node that it build block by a private process ... INVALIDATE by the new policy of Compact Block.

Code:

+Compact Block support (BIP 152)
+-------------------------------
+
+Support for block relay using the Compact Blocks protocol has been implemented
+in PR 8068.
+
+The primary goal is reducing the bandwidth spikes at relay time, though in many
+cases it also reduces propagation delay. It is automatically enabled between
+compatible peers.
+[BIP 152](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki)
+
+As a side-effect, ordinary non-mining nodes will download and upload blocks
+faster if those blocks were produced by miners using similar transaction
+filtering policies. This means that a miner who produces a block with many
+transactions discouraged by your node will be relayed slower than one with
+only transactions already in your memory pool. The overall effect of such
+relay differences on the network may result in blocks which include widely-
+discouraged transactions losing a stale block race, and therefore miners may
+wish to configure their node to take common relay policies into consideration.

[ownageplocks]

Thanks everyone for your help. I'm sure this will hopefully resolve itself shortly, we will see.

[andrew24p]

If its taking two hours you didnt set a decent fee.

[AngryDwarf]

I don't think that site displays unconfirmed transactions, only confirmed ones.

this site display unconfirmed transactions when they are EMIT ...

others blockexplorers use miners to have a pre-block vision with cheating transactions.
i don't use this blockexplorer for this.

on the site that i have linked, i see the realtime mempool with the original and FORCED rules of the Bitcoin network.

not the cheating privat mempool of a miner node that it build block by a private process ... INVALIDATE by the new policy of Compact Block.

Code:

+Compact Block support (BIP 152)
+-------------------------------
+
+Support for block relay using the Compact Blocks protocol has been implemented
+in PR 8068.
+
+The primary goal is reducing the bandwidth spikes at relay time, though in many
+cases it also reduces propagation delay. It is automatically enabled between
+compatible peers.
+[BIP 152](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki)
+
+As a side-effect, ordinary non-mining nodes will download and upload blocks
+faster if those blocks were produced by miners using similar transaction
+filtering policies. This means that a miner who produces a block with many
+transactions discouraged by your node will be relayed slower than one with
+only transactions already in your memory pool. The overall effect of such
+relay differences on the network may result in blocks which include widely-
+discouraged transactions losing a stale block race, and therefore miners may
+wish to configure their node to take common relay policies into consideration.

Like I said, the transaction was in my mempool which has quite relaxed settings, so it had propagated across part of the network. But after reading that BIP 152, yikes! I suppose the only good thing about that solution is that it doesn't have assert(0), otherwise I prefer x-thin to that economically manipulative implementation.

[ownageplocks]

One transfer came at T-6HR and the other T-9HR not too unhappy.