From: Mike Hearn <mike@plan99•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Testnet block explorer
Date: Fri, 27 Dec 2013 18:05:12 +0000 [thread overview]
Message-ID: <CANEZrP398MCW6CdQLo78DtQ7HWY4f1TMkj32Fm2dTrKcUT09cg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
For a long time the only block explorer for testnet has been the original
blockexplorer.com, which is unfortunately often broken / behind / slow and
not really maintained any more.
There is now a new one, here:
https://www.biteasy.com/testnet/blocks
There's also a REST/JSON API for it.
Please note one curiosity of this block explorer is that the coinbase tx
doesn't necessarily come first in the listing (it's sorted by "time
received", see).
Other interesting thing to note: this site is built using bitcoinj. The
author can be contacted on IRC sometimes using the nick damethos.
[-- Attachment #2: Type: text/html, Size: 850 bytes --]
next reply other threads:[~2013-12-27 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 18:05 Mike Hearn [this message]
2013-12-27 18:08 ` Mike Belshe
2013-12-27 19:23 ` Melvin Carvalho
2013-12-27 21:36 ` Eric Lombrozo
2013-12-27 21:48 ` Eric Lombrozo
2014-02-16 13:45 ` Melvin Carvalho
2014-02-16 14:49 ` Matias Alejo Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP398MCW6CdQLo78DtQ7HWY4f1TMkj32Fm2dTrKcUT09cg@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox