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

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 

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.

+1

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

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?

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.

Same here. Similar problem.

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.