Transaction Not Confirmed in over 7 hours

[Rulishix]

Can anyone tell me what's wrong with this transaction? It's not confirming and my .3 btc are not showing up in my MultiBit wallet. Will it confirm overnight or what?

https://blockchain.info/tx/7306496157644a0687a16e4caedc684263482a98060c56624e5e09e58facfc36

[1715216084]

1715216084

[1715216084]

1715216084

[1715216084]

1715216084

[1715216084]

1715216084

[jl2012]

It has a dust output: 0.00000001. Ask the sender why he did so.

[BurtW]

Yes, a bit strange.  Whoever sent this to you did this:

182sd6f8TuLiGqNc5YMbmnLjYfWhne4XW5 - (Unspent) 0.00000001 BTC - strange
1M7Z9DodWydyr96bPeZmtEvSiAD4qDzW3H - (Unspent) 0.30 BTC - To you
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E - (Unspent) 0.01531233 BTC - change, normal

+ 0.0001 fee

strange send in the first line might be what is holding it up.  You probably have to wait for the transaction to get thrown out and then ask him to send it again but this time leave out the one satoshi dust transfer.

Also:  Since size 3174 (bytes) it would not hurt to add a bigger fee.

[DeathAndTaxes]

Since OP decided to cross post this everywhere here is my response from the other thread.

OP don't do that again.  It is annoying to find the same post in multiple sub forums.  The other forum is a better location this isn't a development & technical discussion it is a request for support.

Insufficient tx fees.  The tx is low priority which means most nodes will require a tx fee to relay.  The min fee for relaying on low priority tx is 0.1 mBTC per KB.  The tx is 4KB (rounded up) so the min fee would be 0.4 mBTC. Miners running reference implementation see txs with fee below the min as free.  It will be included whenever a miner has space for a free transaction.  It could be the next block or it could be next week.

It also has an output below the dust threshold which means most nodes and miners will simply drop this tx as invalid.  Did you create this tx?  It shouldn't be possible to create a tx like this using the reference client (or one which follows similar rules).

If you send a tx without fees (and less than min for low priority tx is essentially zero) then you are relying on the generosity of miners to include it when they can.
If you create a non-standard tx then all bets are off.  It may never get relayed by anyone to any miner or one or more miners may simply drop it from the memory pool.

In hindsight blockchain.info already said essentially the same thing

Confirmation Warnings: Low priority.  This transaction has a very small output and is none* (sic) standard.  The transaction fee is less than recommended.

* none standard should be non-standard.

[Rulishix]

Thanks, guys for the answer. Sorry for the crosspost.

[undeadbitcoiner]

Summary
Size    3174 (bytes)
Received Time    2014-02-17 07:12:16
Estimated Confirmation Time    Unknown (Low Priority)
Relayed by IP    Blockchain.info

7306496157644a0687a16e4caedc684263482a98060c56624e5e09e58facfc36
1EC9SoJJhexoyd5KMDivtbEmueUPanWy4F (0.00794262 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.2 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.007 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.00255754 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.02 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.006 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.0009 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.00112 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.00096094 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.005 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.0011125 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.002 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.0058 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.01111874 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.007 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.0069 BTC - Output)
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E (0.03 BTC - Output)
      
182sd6f8TuLiGqNc5YMbmnLjYfWhne4XW5 - (Unspent) 0.00000001 BTC
1M7Z9DodWydyr96bPeZmtEvSiAD4qDzW3H - (Unspent) 0.3 BTC
1GLauaacoDT5jeCcQFk3AGAgqgyXjh5k2E - (Unspent) 0.01531233 BTC

[Rulishix]

Is that what he did? Goddamn! Fuck me. That will take forever to confirm, huh?e

[erono]

I once waited a Transaction to Confirmed for 36 hours.

[Amitabh S]

This will likely never confirm. Who sent you this? If you don't mind, please share this info. Smells fishy as the sender likely hopes it will get dropped after sometime.

[serje]

This will likely never confirm. Who sent you this? If you don't mind, please share this info. Smells fishy as the sender likely hopes it will get dropped after sometime.

The owner of a pozi sent this but it seems the owner was smart enough to make automated transactions but he used blockchain.info wallet that's why his address appears so many times in the sent side of the window because blockchain.info wallet every time you make a transactions makes a temporary deposit address with the same name to put there some coins just like qt client but at blockchain you have the same address

I've experimented this on my own https://blockchain.info/tx/4dd869bcd2db2becbfe0a7435d12afcc67fe13a5c5c9e3c955c5fa97aa630ee2


and decided I will not use blockchain.info again until they make something with this

[DeathAndTaxes]

This will likely never confirm. Who sent you this? If you don't mind, please share this info. Smells fishy as the sender likely hopes it will get dropped after sometime.

Yeah it could be a good setup for a double spend.  Attacker creates tx, feigns ignorance on why it won't confirm.  After the deal is completed, miners eventually drop the tx from memory pool and attacker double spends.  No real "race" because the legit tx was kneecapped at the starting line.

[serje]

This will likely never confirm. Who sent you this? If you don't mind, please share this info. Smells fishy as the sender likely hopes it will get dropped after sometime.

Yeah it could be a good setup for a double spend.  Attacker creates tx, feigns ignorance on why it won't confirm.  After the deal is completed, miners eventually drop the tx from memory pool and attacker double spends.  No real "race" because the legit tx was kneecapped at the starting line.

I doubt the attacker had that in mind as his pozi is now ruined because of this
this was a guy who sent 0.3BTC to his ponzi and after 2 days of being stuck at paying him back 0.36BTC he decided to refund him with 0.3BTC
but it seems the ponzi owner is a newbie to blockchain wallets also not only on this forum

name of pozni is nisaai search it up

[BurtW]

If he is using blockchain.info then didn't he have to add the dust output himself?  Why did he add the dust output?  Best reason I can think of is to delay the payment (probably forever) as stated above.  Sounds fishy to me.

[Rulishix]

Transaction is finally on my Multibit client but it's taking forever to fucking confirm! It's up to 10 peers right now. Lol.

[DeathAndTaxes]

Transaction is finally on my Multibit client but it's taking forever to fucking confirm! It's up to 10 peers right now. Lol.

Since most peers are droping the tx the best thing the sender can do is delete the original tx and then create a new one with proper fee, and no dust outputs.  It should propogate the network very rapidly (as only nodes which kept the original will block it) and will be included in a block by a miner quickly.

This transaction in theory could not confirm in decades if no miner either is relayed the tx or chooses to not drop it from the memory pool.