Blockchain.info - Bitcoin Block explorer & Currency Statistics

[justusranvier]

BIP32 support means there's no reason for Blockchain.info wallets to reuse addresses.

[1714306410]

1714306410

[mutex]

I'd like a refresh button in the new blockchain chrome extension.

[malevolent]

There's a problem with opening wallets with 20 000 iterations of PBKDF2, couldn't log in at first, got a "syntax error" message, after managing to log in all my BTC addresses were zeroed, and loading one of the previous wallet backup only helped after trying about 10 times (with different backup). My browser is Chrome (newest version).

[picobit]

I got 3 non-confirming transactions, age 1-9 hours now. Standard fee settings. Is there anything I can do to speed things up or is there a problem with the blockchain wallet?

Unfortunately, blockchain.info sometimes make transactions without a fee, if it judges that a fee is not strictly necessary (at least the iPhone app often does that).  They can take forever to confirm, I recently had one taking slightly more than two days!  There is very little you can do; i had planned on waiting till in vanished from the memory pools of the net and then double-spend the coins by importing the private keys into Multibit.  But fortunately it finally confirmed.

For this reason I usually use the advanced setting and specify a fee myself.  Imagine doing a face-to-face localbitcoin transaction and the other guy insisting to wait for the first confirmation 

[coinpr0n]

[Chrome extension (maybe others?)] Using Custom Send to send a transaction to multiple addresses, one of the addresses was invalid when I clicked Review Payment: the whole interface locks up leaving all buttons useless. Suggestion: would be nice if I could remove / correct that one address without having to hard-refresh and start from the beginning.

[DannyHamilton]

Imagine doing a face-to-face localbitcoin transaction and the other guy insisting to wait for the first confirmation 

I REALLY wish a few of the larger pools would implement "child pays for parent".  It should increase the profits of the pool, and would eliminate problems like this.

[giantdragon]

Could you reduce minimum transaction amount for the Receiving API? 0.001 BTC is worth $0.7 now...

[rme]

Android app still adds 0.0005 fee but i have configured to send normal fee (0.0001) in the website.

[stellan0r]

I got 3 non-confirming transactions, age 1-9 hours now. Standard fee settings. Is there anything I can do to speed things up or is there a problem with the blockchain wallet?

Unfortunately, blockchain.info sometimes make transactions without a fee, if it judges that a fee is not strictly necessary (at least the iPhone app often does that).  They can take forever to confirm, I recently had one taking slightly more than two days!  There is very little you can do; i had planned on waiting till in vanished from the memory pools of the net and then double-spend the coins by importing the private keys into Multibit.  But fortunately it finally confirmed.

For this reason I usually use the advanced setting and specify a fee myself.  Imagine doing a face-to-face localbitcoin transaction and the other guy insisting to wait for the first confirmation 

thank you, i will do that in the future. all 3 tx are confirmed now, in the same block..

[sunnankar]

I'd like a refresh button in the new blockchain chrome extension.

+1

[cardcomm]

I'm having a problem with a stuck "shared send" transaction now for more than 24 hours.  I've sent a couple of support requests, and even provided more info that they asked for.

But there is still no resolution. I'm not even sure what happens in a shared send situation if the blockchain eventually gives up on the transactions. BTW, the blockchain.info shared send tool automatically added the transaction fee of 0.0001. That should have been enough, but I guess more may have made it move faster on the blockchain. I wish there were a way to set the fee for shared send.

Anyway, I'm getting stressed here - I need these funds. Does anyone have any suggestions on possible problems or solutions? I thought it was blockchain slowness at first, but now I think it's something more.

Just in case block chain.info support monitors this thread, my support ticket number is 12279. Help Please?


(This is the second time in a row "shared send" has been delayed for many hours for me. Doh! ) 

[chrisrico]

It appears the Firstbits API is broken. Neither of the two API calls return any data.

[MayDee]

Would be very nice if we Norwegians could get the Norwegian Krone as a currency option

Support for NOK in the Iphone app would be perfect for me 

[scribe]

Getting this error every time I send some coins: "An outpoint is already spent [(94024681, 1)]" - using the Firefox extension, v3.1.3.

Doesn't seem to affect the transaction though. Any ideas?

[nimda]

Getting this error every time I send some coins: "An outpoint is already spent [(94024681, 1)]" - using the Firefox extension, v3.1.3.

Doesn't seem to affect the transaction though. Any ideas?

I had an error sending coins where the account balance was told as 0 - "not sufficient funds." Resending again worked fine. I was using custom send.

[cardcomm]

I'm having a problem with a stuck "shared send" transaction now for more than 24 hours.  I've sent a couple of support requests, and even provided more info that they asked for.

But there is still no resolution. I'm not even sure what happens in a shared send situation if the blockchain eventually gives up on the transactions. BTW, the blockchain.info shared send tool automatically added the transaction fee of 0.0001. That should have been enough, but I guess more may have made it move faster on the blockchain. I wish there were a way to set the fee for shared send.

Anyway, I'm getting stressed here - I need these funds. Does anyone have any suggestions on possible problems or solutions? I thought it was blockchain slowness at first, but now I think it's something more.

Just in case block chain.info support monitors this thread, my support ticket number is 12279. Help Please?


(This is the second time in a row "shared send" has been delayed for many hours for me. Doh! ) 

This transaction cleared for me finally. The BTC went in at around $640 US and soared above $800 US. By the time they FINALY came out of "shared send" they were worth $580 USD. Not a catastrophe, but a signifigant loss none the less, considering it cost me a business opportunity. 

Anyway, on to my real point:

I'm a newbie at it, but I did my best to track my way BACK through the transactions to find the ONE transaction that held up the long string of shared send transactions after it (mine being one of them).

What I found what that this transaction:
ec9f973b94234ea19812fa02d7edee8e98193d46b826b9597719d500e664f9c7

It had a LOT of inputs, a size of 4373 (bytes), and paid ZERO transaction fee. In other words, it's a terrible prospect for fast propagation through the blockchain.

This transition caused the entire string of transactions dependent on it to get held up for many hours, costing untold amounts of money. It seems that transactions such as this questionable one should be excluded from shared send activity, especially during periods of known high load.

While I welcome all thoughts and responses, I'm hoping for an official blockchain.info take on my observations.

Again, I could be way off as to the cause. I just know the last two of my shared sends have taken a LONG time to complete, to the point where they have been worse than useless. Certainly, other transactions during the same period WERE taking a long time to complete, but most completed far sooner than 30+ hours.

I'd love to see some sort of solution to this issue. Maybe it's simply a matter of adding a feature to check for the likelihood of confirmations before unclipping in a shared transaction.

Thanks for all your hard work. If this post belongs somewhere else, Mods please fell free to re-locate.

[picobit]

This transition caused the entire string of transactions dependent on it to get held up for many hours, costing untold amounts of money. It seems that transactions such as this questionable one should be excluded from shared send activity, especially during periods of known high load.

While I welcome all thoughts and responses, I'm hoping for an official blockchain.info take on my observations.

I agree, such a transaction should be excluded from being reused in shared send.  I have no clue if that is practically possible.  NEVER use shared send or similar for time critical stuff, they do not guarantee that the money come back out quickly (indeed with the old mixed send, they mentioned that it could take a while).  Instead, make an extra wallet, do a shared send to that wallet today, and then use that wallet next time you send.

Also, it is unlikely that blockchain.info see you post, they are badly undermanned compared to the size of their operation (but then apart from shared send it is basically free).  You should contact their support directly, that increase the chance that they see this issue.

[coinpr0n]

Getting this error every time I send some coins: "An outpoint is already spent [(94024681, 1)]" - using the Firefox extension, v3.1.3.

Doesn't seem to affect the transaction though. Any ideas?

Same here. Similar problem.

[rammy2k2]

how can we buy BTC with SMS ? i cant find any option in my wallet 

[coinpr0n]

how can we buy BTC with SMS ? i cant find any option in my wallet 

I don't think that's an option. Correct me if I'm wrong.. but you cannot buy BTC on Blockchain.info. It's a wallet service, not an exchange.