Blockchain.info - Bitcoin Block explorer & Currency Statistics

[paraipan]

like it, it would be nice to view amount transfered instead of that big black arrow though 

[piuk]

why you ban me bro?

nah for some reason cant reach your site from here, but i an when i proxy.

Strange, you should be able to. Can you access http://81.187.238.52/bitcoin directly? If not try a traceroute.

The Summary for a block shows "Previous block" but the value displayed is not the block number but the index, which makes it confusing.

Fixed, thanks.

like it, it would be nice to view amount transfered instead of that big black arrow though  

I'm trying to make it clear for the average user which way the money is being sent. I'll see if i can come up with any better ways to do it.

Some changes:

• Added 7 day averages for all graphs
• Fixed a few design issues on ie
• Modified my bitcoind to accept double spend transactions

On my todo list:

• Bitcoin days destroyed (thanks Stephen for explaining)
• Solid coni support
• Complete the move to the bitcoind mysql backend and remove rpc polling
• list addresses with the highest balances

[Exonumia]

Strange, you should be able to. Can you access http://81.187.238.52/bitcoin directly? If not try a traceroute.

By IP address it loads instantly for me.

By the url ( http://pi.uk.com/bitcoin ) I got all sorts of issues but it now back to normal.

Very cool site by the way... good job!

[piuk]

Strange, you should be able to. Can you access http://81.187.238.52/bitcoin directly? If not try a traceroute.

By IP address it loads instantly for me.

By the url ( http://pi.uk.com/bitcoin ) I got all sorts of issues but it now back to normal.

Very cool site by the way... good job!

This maybe due to me stopping and starting the server, as i'm still finding bugs. Hopefully things should get more reliable over time.

[Clark]

This is a really cool product. I love your charts from the first page as well as the way you use large arrows to show transactions to and from an address.

Way to go!

[piuk]

Due to a database bug, I have to re-import the last 2k blocks - some parts won't function for at least an hour.

[Clark]

Feature request: Show date/time on transactions.

[piuk]

Feature request: Show date/time on transactions.

The problem with this is transactions don't have a time associated with them when sent. So there are two options:

- Record the time my client receives the transaction (which would mean no times for old transactions)
- Use the timestamp from the block the transaction was included in (no times for unconfirmed transactions)

Which do you think would be best?

[Clark]

Just put the timestamp from the block. That makes more sense because we would get transaction times for all the transactions. Also, a transaction isn't really verified until it has been included in a block.

Maybe just make a note about the time being that of the block instead of the transaction itself.

[doktor99]

On my todo list:

• Bitcoin days destroyed (thanks Stephen for explaining)
• Solid coni support
• Complete the move to the bitcoind mysql backend and remove rpc polling
• list addresses with the highest balances

+1 to notion of adding the Bitcoin DD (days destroyed) stat.

One other comment: where do you get $1000 / 2 years for 1 GHash? Is that approximately 50% depreciation per year on a rig which costs $1/MHash/s? Don't disagree with the number so much as interested in how you derived it.

[doktor99]

I've created a site similar to block explorer with a couple of improvements:

• Includes orphaned blocks which can be used to track possible double spends
• Estimates the actual volume of BTC transacted (not just BTC sent)

The site can be found at:

http://pi.uk.com/bitcoin

All ideas and feedback welcome.

Is the site down? As of 3:38pm PST, this appears to be the case. Wanted to ask a question about the calculation method on transactional volume.

[d'aniel]

I imagine doing a statistical analysis of the distribution of address balances might reveal useful information.  E.g. the time evolution of the median balance size might show how the number of users has changed over time, or the skewness evolution may say something about the rate of diffusion of bitcoins.

It'd also be nice if you made the usable data available for download in csv format so people who don't know how to get it from the block chain, but who are otherwise good at analysing it, can play around with it.

[doktor99]

What is the logic used to estimate the transaction volume?

Do you simply always to the smaller 'To' amount as the transaction amount (right of your arrow in the transactions)?

[piuk]

+1 to notion of adding the Bitcoin DD (days destroyed) stat.

One other comment: where do you get $1000 / 2 years for 1 GHash? Is that approximately 50% depreciation per year on a rig which costs $1/MHash/s? Don't disagree with the number so much as interested in how you derived it.

The average upgrade cycle for gamers is somewhere between 18-24 months (can't find the link where i read it now). After two years old cards won't be worth running compared to the newer competition, there probably is some resale value which isn't calculated in.

What is the logic used to estimate the transaction volume?

Heres the method. Basically common transactions "1 in ->2 out" it takes the smallest value, ">2 in -> 2 out" it takes the largest, otherwise total all.

public long getActualBTCSent() {   
       if (blockIsMined()) {
          return 0;
         
      //If a transaction transaction has more than two inputs and two outputs we take the largest output
       } else if (nInputs >= 2 && nOutputs == 2) {
         return Math.max(getOut().get(0).getValue(), getOut().get(1).getValue());
      //If a transaction has one input and two outputs we take the smallest output
      } else if (nInputs == 1 && nOutputs == 2) {
         total = Math.min(getOut().get(0).getValue(), getOut().get(1).getValue());
         
      //None simple transaction total all outputs
      } else {
         long total = 0;
         for (Output output : getOut()) {
            total += output.getValue();
         }
         return total;
      }
}

[goodlord666]

Very well done!


Can you add timestamps to the transaction history of addresses?

[piuk]

Very well done!


Can you add timestamps to the transaction history of addresses?

I've added timestamps to the transaction themselves. Unfortunately due to the way my mysql tables are partitioned it's quite slow to lookup a block from a transaction so I probably won't be able to add timestamps to the transaction history.

I've also added the ip of the node who first relayed a transaction.

[piuk]

I've added the a list of large recent transactions at http://pi.uk.com/bitcoin/largest-recent-transactions

Also i've rewritten a lot of the bitcoin networking code so my client can now connect to around 2000 nodes. I'm running two clients so have a pretty good chance at intercepting double spends.

[piuk]

Added search by ip. For example if you lookup eligius's posh pool ip you can see their payouts http://pi.uk.com/bitcoin/ip-address/78.47.187.255. Data coming for blocks soon.

[piuk]

Finally got round to adding bitcoin days destroyed:

http://pi.uk.com/bitcoin/charts/bitcoin-days-destroyed-cumulative?timespan=180days&showDataPoints=false&daysAverageString=1

Please could someone double check my formula:

days destroyed for one block =

for every transaction
   get the timestamp of the owning block in seconds (t1)
     for each input
       get the value of the previous output (v1)
       get the timestamp of the previous output's block (t2)
       daysDestroyed += v1 * ((t1 - t2) / 60 / 60 / 24)

 
I don't know if Abe is calculating it in a similar fashion, but for me it is very slow (takes roughly 10 mins for per 24hour period)

[Andrew Vorobyov]

Can you add horizontal line showing BTC supply rate at http://pi.uk.com/bitcoin/charts/bitcoin-days-destroyed?timespan=1year&showDataPoints=false&daysAverageString=7 chart