Topic: Bitcoin Block Explorer - page 3. (Read 29682 times)

As I've said before in other threads, I believe Namecoin will inevitably fail because its economic model is broken. So I won't support it.


I don't want to make my code public now. Maybe later.

Would you consider setting up BBE for namecoin's block chain?

If you are not interested in doing so, would you release the source so someone else could host it?

thanks!

New Real-Time Stats page:
http://blockexplorer.com/q/mytransactions

It allows you to get all transactions for given addresses. This could be used to make a simple Bitcoin client.

Examples:
http://blockexplorer.com/q/mytransactions/1Cvvr8AsCfbbVQ2xoWiFD1Gb2VRbGsEf28
Dumps all transactions for 1Cvv...

http://blockexplorer.com/q/mytransactions/1Cvvr8AsCfbbVQ2xoWiFD1Gb2VRbGsEf28/0000000000034b1d01d6296f7f6f46d3ba4e6cb358b8eb74d5ff7ff492e4e23a
Dumps all transactions for 1Cvv... since block 34b1...

http://blockexplorer.com/q/mytransactions/1Cvvr8AsCfbbVQ2xoWiFD1Gb2VRbGsEf28.1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Dumps all transactions for 1Cvv... and 1NXY...

The page has good support for If-None-Match, so it can be polled without using much bandwidth.

Right now only address transactions are shown, since that's all you'll usually want, but I could support all transaction types if there is a demand.

http://blockexplorer.com/testnet is now using the new testnet.

The format of http://blockexplorer.com/q/nethash has changed. It needed built-in explanatory text, I think. The averages for rows that occur on a retarget are hopefully improved now, also. (I noticed that it was severely off when the most recent retarget showed 900+ ghash/s...)

This is really cool, knowing this, I'll be able to sleep much better. thanks a bunch.

It eliminates spent outputs. The total value of unspent outputs should equal the total BTC in circulation (as it does).

The LEFT JOIN matches each output with the input that spent it. If inputs IS NULL for a row, then the output is unspent.

I intend to release my getblock-to-SQL script at some point in the far future, since it allows easy access to stats like this. It's much too messy right now, though.

Thanks. Looks this is what I've been looking for. I don't quite understand your table definition though. Does "WHERE inputs IS NULL" restrict result only to coin-generation transactions?

It checks out on my database:

My database updating script will refuse to accept a double-spend, though I doubt I will catch something that Bitcoin itself doesn't.

wow, that's a bitcoin data gold mine.

I know people here have put great faith on bitcoin's ability of preventing double-spending, or creating coins out of thin air, because that's one of the cornerstone of this currency and the foundation of bitcoin's value.

But as a paranoid person as I am, I feel much more comfortable if there's a way to independently count (or estimate) the total amount bitcoins in circulation, without relying on 50 btc x (# of blocks) calculation. -- i.e. can we look at all blocks, add up all the amount flowing into recipient addresses, then subtract whatever flows out of these addresses, and get the total amount of bitcoin in circulation?

This way, if there's some evil government or evil scientist finds a way bypassing the double-spending prevention mechanism, they will have to expose themselves via block chain data.

I mentioned this a while ago on IRC, but hardly anyone seems to be using it:
http://blockexplorer.com/q/nethash/144

Possibly I need to explain the columns:
- blockNumber: Each row looks at a section of blocks (the section size is specified by the query parameter). This is the latest block included in the section. So the section includes data from the last row's blockNumber+1 up to this blockNumber. The first row looks back to block 1.
- time: Unix time at blockNumber.
- target: Full decimal target at blockNumber.
- difficulty: Difficulty at blockNumber.
- hashesToWin: Average number of hashes required to solve a block at blockNumber's difficulty.
- avgIntervalSinceLast: The average number of seconds between each block in the section.
- netHashPerSecond: Number of hashes the network is doing per second in this section. Calculated by comparing avgIntervalSinceLast to hashesToWin.

This data can be used to make a very nice graph of network power and difficulty.

There are now Real-Time Stats tools for the testnet, too:
http://blockexplorer.com/testnet/q

Now is a good time to mention that testnet BBE will not automatically switch to a new chain if anyone attempts to replace the entire chain, but will stop updating until I switch it over manually. (This is to prevent mainline blocks from being lost in case an attacker finds a way to destroy all Bitcoin clients' block databases.)

BBE now publishes RSS feeds for addresses. Your browser should be showing you an RSS option on all address pages. Should I include a human-readable link, too, you think?

This is useful for tracking your own transactions without having to run the client or log into your e-wallet. You can also get emailed about your transactions by using one of the many RSS-to-email providers.

The feed shows the last 20 received transactions, with the newest transactions first. Sends are not shown since they are mostly uncontrollable. The links all point to the address page right now -- eventually I will have them highlight the specific transaction on that page.

HTTPS access to http://blockexplorer.com/q and the rest of BBE will be offline for 2-5 days starting a few days from now. If anything uses the tools over HTTPS, change it ASAP or prepare to have your packets rejected for a few days.

(I'm making some hardware+software changes that require me to move BBE to a different computer temporarily, and I don't want to move the private key for security reasons.)

Awesome, theymos! Thanks for that.

It'll be handy to see during the next spam flood.

ByteCoin

Data sizes are now shown for transactions and blocks.

A+

And now HTTPS, too:
https://blockexplorer.com/

BBE and Real-Time Stats are now at a more easy-to-remember location:
http://blockexplorer.com/
http://blockexplorer.com/testnet/
http://blockexplorer.com/q/

All old links should redirect to the equivalent page at the new domain. Tell me if any links fail to do so.

It's a very handy tool.

It would be good (for me at least) if there was a field in the "Block" view that gave the length of the block in bytes. It would be nice to have a size column which gives the transaction size in bytes and a priority column which shows the priority as calculated using the recently implemented formula.(Priority no sooo important to me at the moment though.)

On the "From" and "To" columns it would be nice to see the "balance" associated with that public key before the transaction so that a coinbase transaction would say for 91812
16va6NxJrMGe5d2LP6wUzuVnzBBoKQZKom:0 +50 = 50
and the other transaction would show as

777ed67c58... 0 1BFrS5LQSTY... : 1 -1 = 0 16QjxpGVX6EF... : 19 -19 = 0   1MCwBbhNGp5hR...: 411.9 +20 = 431.9

You can imagine that it's handy to have this info at block level without having to drill down to transaction or address level.

Also, it would be very interesting to have a list of unspent addresses and their balances. Obviously this total should add up to the currentblocknumber*50

If you wanted to be a hero you could work out how much space could be recovered from the block chain by removing spent transactions and stubbing the merkle tree down as much as possible. I suspect it wouldn't be much at the moment.

If you wanted a tougher task and be a real hero you could create a graph of bitcoin transactions with each address being a node and each transaction being a directed edge. You could display the thickness of the edges as being the number of transactions or the total value and see how many isolated graphs the transactions fall into.

The last two are harder more long term projects but the block page changes would be very handy for me in the short term.

Thanks theymos

ByteCoin