Topic: [Locked] PPC block explorer - Please use the new Cryptocoinexplorer thread (Read 18552 times)

Nice work dreamwatcher i have updated the list of sites for PPC here http://ppcointalk.org/index.php?q=node/7 to show your new site

WWW.PPCEXPLORE.ORG is moving to a new server:



WWW.CRYPTOCOINEXPLORER.COM

PPC Explorer is now available at port 2750 (WWW.CRYPTOCOINEXPLORER.COM:2750)

TRC Explorer continues at  port 3750 (WWW.CRYPTOCOINEXPLORER.COM:3750) or just WWW.CRYPTOCOINEXPLORER.COM until I make a home page to choose which engine to go to.

Web page operators linking to either one will probably want to use the direct port URL. Eventually PPCexplore.org will point to this server, so change your links now if you direct link.

WWW.PPCEXPLORE.ORG will eventually point to the new server and home page to choose between coin search engines.

IT would be great if you could add terracoin support. I was going to try and work on this myself but haven't had a chance yet. I'd be more then willing to do a little donation for that! cheers!

Hi dreamwatcher,

You have done great work and is doing great service to the ppc community. Hope you can keep up the good work!

btw how much are you paying for the VPS and what's the resource requirement for your VPS (ram, bandwidth, storage etc)?

yes please ... i'd like to say new site... but just a sub search on site till u get more donations
I will have to get back to u on this as it is late... but love everything info wise i see so far
Shame on us all I will send u a donation though I do not have much at the moment... but as i like and use ur site and appreciate ur development and work, when I get more I shall donate more

Nice to hear ur programming tails and enjoy the python and keep up the excellent work XD

I was wondering if there would be any interest in adding Terracoin either as another searchable currency on PPCexplore.org engine or as a new site?


The PPC GUI with block explorer is still in the works, as of now it is in a prototype stage.

The beta and final release will be (almost for certain) written in Python and QT. The prototype is written in .net, only because it allows me to put more concentration on the logic development itself rather then the syntax and structure of a newer language to myself. (I can write in .net while sleeping. Python is not exactly "old hat" to me, though I am  thoroughly enjoying exploring it deeper).
 
I chose Python because of its great ability for cross platform and some really nice BTC tools have been written in Python that I can borrow into my code.

As a side note: I was going through a box the other day, when I came across some old programming assignments from my college days. I must have drove my professors mad    Some of the code is quite "unconventional", but sure got the work done. I loved reading some of the comments in the margins.




I STILL NEED SUGGESTIONS ON WHAT THE USERS WOULD LIKE TO SEE IN TERMS OF FEATURES.


I will be including the ability for the client to directly handle a PPC link in a web page the same way way Bitcoin does now by bringing up a transaction window already filled with Send to address and amount.

I may include some custom code for the "Satoshi Roulette" site to make it more convenient and fun.



Now for a bit of seriousness:

I do not mind volunteering my time and effort to help with the support of PPC.

However, the VPS I use to host PPCEXPLORE.ORG does have a real cost attached to it.

I have thought about advertising, but honestly did not really like what I saw in terms of the types of advertising that would be pertinent to the people using the site.
I do not want the site to turn into a pop-up, advertising box hell.  Some of the things advertised looked downright shady to me.

To date I have not received any donations that I know of. (If you have, please let me know if I missed it)

I am only asking for help with the cost of hosting. Although not incredibly expensive (Yet, as the coin grows, so will the need for a bigger VPS ! ), I have put some serious amount of hours in developing and running the site and sometimes feel double hit when to bill comes for the VPS. (Again, this is not about me getting paid for time and effort. I am more than happy to donate that.)


Anyway, Please post with suggestions on features with a new client. I really want to make this client something special.

Although not directly related to PPC explorer or my current project, I came across this list that I think a few of the readers here would enjoy:

http://listverse.com/2011/02/17/top-10-truly-bizarre-programming-languages/

Thank you so much for your explanation's  

Height is really just another way of saying block number. If you notice the block number and height are the same. Height is what clients use to determine which chain is the correct one if multiple chains present themselves. The chain with the greatest height is considered to be the official chain.

Version is just an internal number that nodes use to make sure that they are using the same version of protocol when communicating.

Merkle root is a hash of all the transactions that effect the block.

Time is the time the block came onto the network, not the time solved.

Nonce is a bit tricky to explain. In ordinary cryptography it is a random number used to make sure a communication is used only once, so a party cannot just capture and send a communication back (such as an authorization). This is commonly referred to as a "replay" attack.
In terms of mining, it gives the header a variance so different hashes can be calculated. If the header remained static one would have an awful hard time getting different hashes to hit the difficulty target. Probably not the best explanation, but the link below can shed more light.

Coins-days destroyed - (From the Wikki) Bitcoin days destroyed for any given transaction is calculated by taking the number of Bitcoins in a transaction and multiplying it by the number of days it has been since those coins were last spent.  From there One can see where "Average coin age" comes from.

IF you want more information : https://en.bitcoin.it/wiki/Protocol_specification

Yes, the time it was made.

The bitmask is kinda the "target" that the algo is aiming for, something st. &1b0668c9 == 0 I think.

The coin age is, if you have 1 coin, that's not been moved, for 1 day, it has 1 coin day. 

If I then transact this coin, the person who receives it starts counting again, and 1 coin day is removed.

If 1000 coins are stored for 15 days, altogether it has 15000 coin days.  If I sent this to somebody, it would destory the coin age, as they start counting again.

I see myself as still learning lol

I would like to get some feedback on what information the average user would like to see in a local block explorer.

The web block explorer gives out some information which I think the average user either does not care about or know exactly what it means.

For example, I will probably leave out nonce and Merkle root in a block display on the local explorer.

Suggestions for items not in the web block explorer that you would like to see in a local block explorer would also be appreciated.

***UPDATE***

PPC Explorer now describes the type of block (POS or POW) and the new coins generated in the header of the Block view page.

POS block transaction listings now separate generated coins from TX fee like the POW block transaction listings did in previous versions.

Nice. I wish there is enough dedicated support on ppc gui wallets. So I can have time to work on daemon features such as the aux transaction I recently proposed.

There were a few gui wallets released but I don't hear about them any more so they appear lacking dedicated support.

My current plan for next year is to implement aux transaction and possibly a web-of-trust app prototype. So most likely gui work is not going to be on my plate yet at least for another year, especially if at least one of the community released gui wallets (such as the one you are working on) gets good support.

Really appreciate all the hard work 

Yes, I will look into that in the next few days.

Sorry about the absence in this thread, it has been a hell of a week.

I have decided that it would take much more time then it is worth to try and do separate searches for POS and POW in ABE. It would require way too much restructuring.

Instead I am going to put more focus on my present project which consists of a PPC GUI client with a block explorer built in.  The present adaptation of the BTC QT client has been invaluable, but lacks some of the functions needed for the unique features of PPC.

The web block explorer will still be supported, and minor changes like Andy requested will still be considered, but I am no longer going to make major revisions to the web PPC block explorer.

Is there any chance on PoS blocks, we have a count of how many coins generated in PoS transaction in the top / header?

It appears updating  PYCRYPTO (Python Cryptography Toolkit) to version 2.6 has fixed the "Unknown" address error

I will begin work on POS & POW search filters this week.

Some API functions will also be updated to indicate POS or POW blocks.

UPDATE:

I have manually updated  PYCRYPTO (Python Cryptography Toolkit). It was version 2.1 in the server repo, I updated to 2.6 on the server.

I will keep an eye out, but please tell me if you find any "Unknown" addresses.

I have uploaded a correct database to the server and now everything should be correct.

It appears there might be a problem with one of the dependencies server side, as the exact same version of PPC explorer I run in a VM locally is always spot on.

If this becomes too much of an issue, I will start remotely maintaining the database until the version of dependencies available to server OS match the same version as the local VM.

Thanks for heads up!!

Edit to Add:

The sign that this is happening is if an "Unknown"  appears in an address space. Please let me know if you see one so I can correct it and if necessary move to another database maintenance method.

Some transactions' hash seem to be wrong in block explorer:

Transaction feba619bc8244581c7e6fcb5115c39f92fa29a5060e3541749433e393988f242 has a different hash in block explorer and block 7479 is having problem with it as input (unknown input)

sunny> ppcoind getblock 00000000000291c0d0b4b790efde847d0fdf174743b90ae7ffe0230520043aa4 true
{
    "hash" : "00000000000291c0d0b4b790efde847d0fdf174743b90ae7ffe0230520043aa4",
    "size" : 1092,
    "height" : 7294,
    "version" : 1,
    "merkleroot" : "6e002b20ee46408f6b29b5a6a6f8905dcfc466493b96470e41c45bc9c90644d9",
    "time" : "2012-09-26 07:27:14 UTC",
    "nonce" : 3825183266,
    "bits" : "1b05ef4b",
    "difficulty" : 11042.61017795,
    "mint" : 975.41000000,
    "previousblockhash" : "000000000005c8dc5d3edf9e065ee8ddab470913e4c89d97b9f115ce0dcef1f8",
    "nextblockhash" : "000000000003976d9d6d07bb15600456486a35c07a340567c9c354181e07588b",
    "tx" : [
        "49217e04493c98ff04b7bdfc91e0b70612ef60c5ab5b2a149421ddbb4db73f1e base",
        " 0000000000000000000000000000000000000000000000000000000000000000 -1",
        " out 975.41 03339f8036 OP_CHECKSIG",
        "feba619bc8244581c7e6fcb5115c39f92fa29a5060e3541749433e393988f242 user",
        " 0fb99e3ee238da0abf92278ce94eee93335efe346adf501818cc99ab9d52c1ae 0",
        " c0a66c842f7700d1566f574597b0fb56d39e45125ac22e690dd7df2faf68adae 1",
        " 07df20ee2064a150d14f80575a9800f8728b79082eeca62639cd4be099c0c046 0",
        " b915c42a295d1e83f44b96a210905d1994fb8e3c7e79f2ea9a855ca16cd87144 1",
        " 887e89e779a5fceae6992832a14f3d9e02bed833afa57d41da7b901333eab3c0 1",
        " out 0.010011 OP_DUP OP_HASH160 eb085e0dc8 OP_EQUALVERIFY OP_CHECKSIG",
        " out 7833.985788 OP_DUP OP_HASH160 0edb666f66 OP_EQUALVERIFY OP_CHECKSIG"
    ]
}
sunny> ppcoind getblock 7703bbb329a66ddf2765e34f90d6f51fb94ae2938b767de60fafb17896c7736d true
{
    "hash" : "7703bbb329a66ddf2765e34f90d6f51fb94ae2938b767de60fafb17896c7736d",
    "size" : 2762,
    "height" : 7479,
    "version" : 1,
    "merkleroot" : "41053f77cf76987805a2f08ec405eee48c1ef58d739c56c5993c1e0b414ef9c2",
    "time" : "2012-09-27 21:17:19 UTC",
    "nonce" : 0,
    "bits" : "1c08d08c",
    "difficulty" : 29.04216204,
    "mint" : 2.18000000,
    "previousblockhash" : "8f2bdea060d80d5781d63eba8d2da183890e760083aa780da363949f07608839",
    "nextblockhash" : "000000000002d10c3d7a632500300916c3bd1b2563e7108c804ced1d89a5ba2c",
    "tx" : [
        "88081cf661bfb045298104932f122834a30ce365639ffbddf0f68fb23cc69eda base",
        " 0000000000000000000000000000000000000000000000000000000000000000 -1",
        " out 0.00 ",
        "46b31ea8684f780e39fb1094d472111c9dfc5f84cc36924f70827db07b895223 stake",
        " 9a7360363484186973ae6a0d4056af391b045e3e41740635ac83cf10a8bc05c2 0",
        " out 0.00 ",
        " out 1036.10 023d651b08 OP_CHECKSIG",
        " out 1036.11 023d651b08 OP_CHECKSIG",
        "7eb01f1ec11fd93df816ed123eb0d6a9f11b36dc3c3981d5add030914becbae0 user",
        " a542b16b3d4f48128bc9861ab83ecdf205217978c3a0807039620a28f2b4863b 0",
        " feba619bc8244581c7e6fcb5115c39f92fa29a5060e3541749433e393988f242 0",
        " 06765d3b7e1eeb1ef5ba0305db9ee8b328d439a93581b767a7d406477f694a5d 1",
        " 9a2bf568934a80659c5558e22ae9b629958535b744500f6a26412e1ef20a5978 1",
        " e63285516411a084ae5517edd0edd30b50b39ed350b48cd694d6b2bb77d71c18 1",
        " 8f2047aff0ddd8bc641aee047ded8c5574c8eaa01c21d5894cd01e66246d0959 1",
        " cd3031778ac0d4a534f403ecf7c4c34a71df459abbfa75b4e38fa0fc4e684668 0",
        " c3dc4d967afc52d7378ae657377e5b0455cfef00443cb9519b6f2ce417dd74e1 1",
        " 31d92c5096ccda4acbf47633789a17be7ff9d6329cf0e179ada718362e5af4d7 1",
        " dd817694241763491ff1b87da3e92f1d72eb6184386cd2ce930f825c7a6eb0bc 1",
        " a15bc95c34c03c27dde1c58dba6f37be3ac99cae469b5abd80ec88c15837dca0 1",
        " 129d830eafd591a1ea8b0783872e8fd8be5626d9ffdc37ecd6f776ed34d63378 1",
        " 98b048ffa53f695220d9e0d872520a37842856ced8689c48f9b99fe15a822780 1",
        " 3f9f9ff1c6ba0a837073bb4e33c80e1d6f5ffe0c9d0bda0cb100f1be0bb78979 10",
        " a2be504ac5bf6c13591eef487d1d45db35b28a2f8fb5cd962e8cf189423bd3e7 1",
        " out 0.010007 OP_DUP OP_HASH160 220b373974 OP_EQUALVERIFY OP_CHECKSIG",
        " out 6269.97 OP_DUP OP_HASH160 9db18ded60 OP_EQUALVERIFY OP_CHECKSIG"
    ]
}