From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Mike Belshe <mike@belshe•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Testnet block explorer
Date: Fri, 27 Dec 2013 20:23:58 +0100 [thread overview]
Message-ID: <CAKaEYhKnRgK2PS4hV2fCws6z69bvsMabL_hEY4OXBv685bCoJg@mail.gmail.com> (raw)
In-Reply-To: <CABaLYCvCcyCdicVRHR-3EhC-8FRB2mZ4AneU0P=skGh_kbSAiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2864 bytes --]
On 27 December 2013 19:08, Mike Belshe <mike@belshe•com> wrote:
> Great!
>
> There is another one at http://testnet.btclook.com/ which provides a
> different view as well.
>
And another at:
http://test.webbtc.com/<http://test.webbtc.com/address/myTPjxggahXyAzuMcYp5JTkbybANyLsYBW>
Testnet does not currently fully function with for creating transactions:
http://test.webbtc.com/<http://test.webbtc.com/address/myTPjxggahXyAzuMcYp5JTkbybANyLsYBW>
Because there's no "unspent" API for getting the unspent values for an
address. If there existed a testnet explorer which would send out those
values (as blockchain.info does with the main net), that would be awesome.
I'm also working on a testnet explorer with semantic web markup so that
it's both human and machine readable.
>
> Mike
>
>
>
> On Fri, Dec 27, 2013 at 10:05 AM, Mike Hearn <mike@plan99•net> wrote:
>
>> 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.
>>
>>
>> ------------------------------------------------------------------------------
>> Rapidly troubleshoot problems before they affect your business. Most IT
>> organizations don't have a clear picture of how application performance
>> affects their revenue. With AppDynamics, you get 100% visibility into your
>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
>> Pro!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists•sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 4916 bytes --]
next prev parent reply other threads:[~2013-12-27 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 18:05 Mike Hearn
2013-12-27 18:08 ` Mike Belshe
2013-12-27 19:23 ` Melvin Carvalho [this message]
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=CAKaEYhKnRgK2PS4hV2fCws6z69bvsMabL_hEY4OXBv685bCoJg@mail.gmail.com \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@belshe$(echo .)com \
/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