This does seem to accurately identify the problem. I will start looking to see if I can find the cause.


Edit: The problem has been solved, thanks to the information from hhanh00! The indices being used to derive public keys from master keys were out of order in one location, which resulted in the wrong public keys being used.

I do not believe this is the problem, unfortunately.

The final 105 bytes would be the redeemScript.


Edit: And here is the redeemScript decoded.

Seems to be working well, good work!

If you don't mind a little self-promotion...

MyChain: http://mychain.io/

An open source block chain explorer in Node.js, with source code available at https://github.com/thofmann/mychain.

I found the reason for this. The missing transaction (the generation transaction for 50 BTC from the block at height 1) on the page doesn't use the now-standard pay-to-pubkey-hash (P2PKH) redemption script. It instead pays directly to the pubkey (P2PK). This is why the lookup for the scriptPubKey_hash in the database failed to find the transaction. I'll have to consider whether this is something that should be changed, but at the moment I think it is most accurate to leave it as it is.

The other transactions that pay to that address use P2PKH, probably from people trying to donate to Satoshi by using the address generated by some other block explorer that displays P2PK scripts as addresses.


---

On a side note, I've restructured the database. This requires syncing with the block chain all over again, so the mychain.io server will not be up-to-date until it finishes indexing the outputs. I've added a Server Status message at the bottom of each page showing the progress when syncing.

The wallet is far from finished. That login sequence you see is basically all I have so far, and it is only experimental. The most common login method right now seems to be the ~12 word passphrases, but I thought this grid sequence was not any harder to remember and would easier to input (particularly on mobile). It is not final, and I am completely open to suggestions for other login methods.

I chose to display data with an accurate description, rather than use misleading terms such as "from address" and "address balance". Deciding the terminology was partly inspired and assisted by luke-jr, but I agree with the decisions I made.

The 'received' value is the largest amount paid to an address by any single confirmed transaction. Any extra transactions are added to the 'possibly received' value. This is because addresses should be used as one-time payment destinations, not as accounts or wallets. Address reuse is bad for privacy as well as security.

That specific address you linked to does not include the generation transaction it should have received in the second block of the chain. That's a bug you just found, and I'm looking into it right now. It seems like it applies to more than just that block. I've marked the issue on Github and will be fixing it ASAP. Thank you very much for reporting it!

Edit: To clarify my answer to your last question, mychain.io does not show the spendable amount an address has because an "address balance" is a misleading term that encourages address reuse (bad). Balances should be displayed on a wallet/account level by your software wallet.

The longer times are probably when looking up something more processor-heavy, such as an address where it must look through the entire outputs database to see what outputs pay to that address. I'll continue to optimize where I can.

Great!

Thanks again for the suggestion. It has been implemented.

This is a nice glossary: https://github.com/oleganza/CoreBitcoin/blob/master/GLOSSARY.md

Thank you for the feedback. Could you be more specific in regards to a lack of responsiveness? The site seems to be running smoothly for me.

It would be great if you could add it to Goochain! Is there anything I could do to help you with this?

If you are looking for a block chain explorer, I would appreciate a review for http://mychain.io. Thanks!

Thanks! I am not currently planning altcoin support, but it would be fairly easy to switch to a different coin's RPC daemon.

That's a great suggestion. I'll add whitespace trimming ASAP.

Next project: MyWallet

http://wallet.mychain.io/
https://github.com/thofmann/mywallet

Lots of work to be done.

Hi!

I've been developing an open source Bitcoin block chain explorer. It is now functional enough for public testing:

http://mychain.io

Please feel free to use it however you see fit. I would greatly appreciate any attempts to break it, especially if any discovered issues are reported on the Github repository: https://github.com/thofmann/mychain/issues. Pull requests are also welcome!

I was hoping to emphasize simplicity and accurate portrayal of block chain data, without promoting any misleading concepts such as "address balances" and "from addresses".

Thank you for the great work on the MyChain (and MyWallet, etc.) logo!

I tweaked it a little bit, but your design is now up on http://mychain.io. The image itself is located here: http://mychain.io/img/logo.png