I've added a "Found by" column to the homepage which shows the ip the block was first relayed by (similar to pident). This won't be 100% accurate due to network latency, my client crashing etc.

The list of known ip's I have are as follows:


Does anyone know Slush's push pool ip?

Great new features. Perhaps RSS/Atom with params would be less taxing on your system?
http://pi.uk.com/rss?address=12345678798,1abcdefgh

Don't get me wrong. The email would be very cool. If it doesn't already, I'd suggest an unsubscribe link in the email. I don't expect people to just randomly pay me money. But I would realistically give an address to a customer/friend and wait minutes, hours, days for a transaction email (rather than polling the block chain periodically) and then forget about the address after I've received payment.

no lo entiendo

Can you describe the use case/steps?

I think your percentages are off a little.

Awesome! Looks great!

That's entirely intentional. It allows them to re-use the merkle tree instead of rebuilding it for every miner who requests work. This is the main reason why I wanted you to have the received times available for blocks.

Very cool. Though is wasn't immediately obvious what you are trying to show. It wasn't until I consulted the previous block and selected "next block(s)" (and there are two of them, EXCELLENT). Perhaps if you showed the previous block (and perhaps the next successful block) your orphaned block page would be immediately obvious.



I don't think you need all the visual hell that I've introduced, but a link to Previous and Next would be helpful. On the other hand, if we did experience a multi-block orphan (attack), then I think you'd need the extra graph nodes to make sense of the attack. Also, an issue I have with your current implementation is that the previous orphaned block with arrow up seems to suggest that it links directly into the next orphaned block which is (in most cases) not true (I suppose that's what you mean to demonstrate with a dotted arrow, which would be more apparent in a context with solid/direct and dotted/indirect linked nodes).

This is how I imagine it, always showing the previous block before orphans.
However, in the case of multi-block orphans (potential attack) it might be easier to visualize if you also added the next node:
By the way, do you know the longest orphan chain we've experienced? Is there any record or does that just get lost after reorg?

I think it's a bit clearer now http://pi.uk.com/bitcoin/orphaned-blocks.