http://www.datatables.net/examples/api/regex.html html Code: Regexp search: <input type="text" class="global_filter" id="global_filter"> js Code: $('input.global_filter').on( 'keyup click', function () { $('#mnlist').DataTable().search($('#global_filter').val(), true, true).draw(); } ); and maybe some css for global_filter Pleeeeeease
Updated the Masternode Monitoring page: HTML v2.0.3 / JS v2.0.8 (20141116) Added regexp search for masternode (and a parameter to pass to the url "mnregexp" to set it). Example to display for pubkey XxMN2deSQzrrXNaToBwA4N2RvhPTesTz5 and XsFNcT4jWLELckQ9LWTeStftG39ATx4HwQ: https://drk.mn/?mnregexp=(XxMN2deSQ...NcT4jWLELckQ9LWTeStftG39ATx4HwQ)#mnlistdetail
Feature request: show all requested addresses even if they do not appear in the mn list, with some kind of color-code flag so we can go figure out why the little bastards disppeared... Maybe pink or purple for being so ghey... When you've got a big fat stack of masternodes, and 4 drop off the network entirely for no reason, it's hard to screen for the missing ones.
I've got 4 that I absolutely cannot get to show up in masternode list. They worked fine initially, changed nothing, refuse to show up. It would be nice if they weren't just ignored by regexp, but were still shown, as unlisted, in purple... OT, but found reason; local client start-many is falsely claiming: This statement is false. All addresses were and still are locked. They all have exactly the same 1000 DRK they started with. Nothing changed. start-many is failing to recognize that which it previously had no problem recognizing. Restart local client. masternode start-many over and over again, it pick up a missing node randomly on one pass or another. After re-running it about 30 times (giving time for propagation, checking masternode list from the nodes themselves), all are back in the list. Sumthin's goofy...
I'm using elberethzone's fantastic API to display at-a-glance masternode balance information at http://drk.monitor.mn/ You can monitor multiple masternodes by adding the full ipaddress(s) into the big Filter By input box. I'll be adding more features this week, and I'm open to suggestions from the community. If you find the site useful, please consider tipping elberethzone. I have a link to his DRK address at the bottom of my site.
elbereth Not sure if you noticed but https://drk.mn/blocks.html#blocksdetail shows "Unpaid" for blocks that were actually paid.
Those payees aren't on the MN list. I emailed Evan about this last night. Edit: Block 175829 paid to this address: https://chainz.cryptoid.info/drk/address.dws?Xv5tUno57WDZ5rGxNVFU3cHJXY1PUyJMy9.htm and it doesn't have a balance, though it looks like it's the first vin and the 1k DRK was moved. I don't understand it. And I did show this to elbereth and discuss with him, he asked me to email evan.
UdjinM6, last night (US time zone) this was on drk.mn: Block 175692 paid to address: XmaySiFee7LKzsVNDmPJSD1YgYgFuuD5ks, but this address wasn't on the MN list. I sent email to Evan, and he explained that, "I looked at the reference node and I don't have it either. The only reason for this would be that specific node went offline right after the payment happened. So it shouldn't get paid again." (Sorry I posted this a few min ago and had to repost because the image didn't show up and I couldn't edit it, had to delete that post.)
Updated the blocks page: HTML v2.0.4 / JS v2.0.8 (20141202) Added link to masternode monitoring page in blocks detail on masternode pubkeys. HTML v2.0.4 / JS v2.0.7 (20141126) Added column in blocks details with expected and actual masternode payment ratio. Also updated the back-end to fall back to 30% vout detection if the pubkey used for mn payments is not on the masternodelist. Additionnally I think the IRC bot is now fixed regarding the mn payment ratio (it was sometimes announcing 25% and sometimes 30%).
elbereth, remember we discussed this address (Xv5tUno57WDZ5rGxNVFU3cHJXY1PUyJMy9) that does not have a balance, yet got MN payment. I just checked my email, Evan replied a few days ago, said:
So that means the guy funded 2 masternodes then discarded the first one but is still getting paid for the second one, that's it?
I guess so. It looks like his second address is XhWdVGfSZoGYcBAv6dCUqJ9wpFkWdbBjBS I'm looking at: https://chainz.cryptoid.info/drk/address.dws?XhWdVGfSZoGYcBAv6dCUqJ9wpFkWdbBjBS.htm This MN has been up since Nov. 2 (?) and no MN payment has gone to it. So I guess his MN payment went to the first address which has 0 balance. Confusing to me but that's how it is, I guess.
Guess we have same problem but now with 35% MN payment blocks MN was payed btw http://explorer.darkcoin.fr/block/000000000000a3caa932924bc24573f1c82be595f12c43283aa0f01df50aed6a
Same problem as before, it was payed but to a masternode that was not on the masternode list. Added a workaround to consider as correct if there is a 35% vout.
Updated masternode page. HTML v2.0.3 / JS v2.0.9 (20150106) Added support to detect version number of new 0.11 "Core".
Recently your site was showing 1740 mn, now it shows 1667 mn, wondering what made it change? (fyi other sites displayed 1660's while yours was displaying 1740. Does it have to do with MN running previous versions that the site doesn't check for? Also noticing that some people are running v 10.17.25, like .3% of all MN, not a large amount by any measure but I'm wondering if anyone can elaborate on that?
elberth fixed something on the page yesterday now the MN count is correct (and the same as darkchild pages)
Updated masternode page. HTML v2.0.4 / JS v2.0.10 (20150117) Backend: Added support for duplicate IPs with several valid pubkeys (you should see a bump of around 250 MNs in the count). Displays both masternode count accurately and the unique IP count. Should not alert/popup when the backend is unresponsive.
Feature request: Additional stats by protocol version (70052, 70053, ...) - currently there is only a chart with "clientversion", which is not accurate being "only latest protocol"
Well actually is all compatible protocols. Afaik they are all compatibles since the one in v10. I would need to keep old nodes running to get masternodes list from them. Not sure it is a good idea as those versions are not new enough to have a complete blockchain and sync running.
