I tried tallying Viacoin on my dev system (PHP5.6/OS X) and my two test systems (PHP5.6/FreeBSD and PHP5.5.4/Mint~Ubuntu) and it works perfectly on all three setups, no hiccups:


I'm not sure what "empty RPC calls" mean. Inspecting individual blocks in the Viacoin chain I don't see anything out of the ordinary. All blocks (including blocks 1-9999) contain coinbases and legitimate transactions with inputs and outputs, and even if they amount to 0 coins this doesn't affect anything.

With the risk of sounding like a broken record, I suspect that you didn't build the block chain with full transaction indexing from the start, as the instructions demand. It's not enough to just add "txindex=1" in your viacoin.conf and start the daemon/wallet up again - you need to remove the entire block chain and rebuild it from scratch, from block 0, with txindex=1 set already from the start.

Let me know how it works out. If you can't get it to work, let me know the details of your PHP environment, your viacoin.conf and so on and we might be able to figure out what's wrong.

RPC Ace v0.7.0 released, introducing optional JSON output and a bit more accurate detection of hashrate and PoS difficulty/stake. This update allows for removing the example block explorer in order to just get PHP array or JSON output for working with the block chain data in other ways - just don't forget to credit the author
 
https://github.com/stolendata/rpc-ace
 
Merry christmas, crypto pioneers.

These are the USE flags required for Gentoo's PHP install

cli curl filter gd hash json pcntl posix readline sockets unicode xml zlib

I dont understand which part of easybitcoin im supposed to edit ?

Anyone else have this issue?

I try but it show blank page.
What am i doing wrong?

Your code on line 35 in rpcace.php should look like this;


if you can not find the bracket "[" that is out of place, look at a few lines before line 35.

If that fail, just replace the file with a copy from the original and make sure that you only change the required variables leaving the rest of the file in tact.

RPC Ace v0.8.0 released, adding optional database storage for faster page generation and reduced burden on the coin daemon, a bit cleaner configuration syntax, and a slightly touched-up version of the example explorer. The database storage is currently rather simplistic, but lays the groundwork for future versions of RPC Ace that will offer transaction/block/address searches and more.

https://github.com/stolendata/rpc-ace


 

Sure. Can you give me any details on errors or so?

For starters you need to give the web server write access to the filename you configure in the DB_FILE parameter, either by making the file itself writable by the web server process, or making the entire directory RPC Ace is located in writable - the first method is preferred. I suspect you may not be used to working in a shell environment, so the simlpest solution in your case is to create an empty file using f.e. Notepad, give it the same name as the filename you set in DB_FILE, upload it to the same dir as RPC Ace, right-click it in your ftp client and look at the file's properties/info and you should see a set of permission flags indicating user/group/other, read/write/execute - click the check box that indicates that the file will be writable by "other", and then give RPC Ace a try again.