Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin initial update Jan 18, 2019
guides initial update Jan 18, 2019
lib CryptoBridge market added Feb 8, 2019
locale initial update Jan 18, 2019
models chart updated Jan 18, 2019
public chart updated Jan 18, 2019
routes initial update Jan 18, 2019
scripts fixes Jan 19, 2019
spec initial update Jan 18, 2019
test initial update Jan 18, 2019
tmp initial update Jan 18, 2019
views CryptoBridge market added Feb 8, 2019
.gitattributes initial update Jan 18, 2019
.gitignore initial update Jan 18, 2019
Dockerfile initial update Jan 18, 2019
LICENSE initial update Jan 18, 2019
README.md initial update Jan 18, 2019
UPGRADE initial update Jan 18, 2019
app.js initial update Jan 18, 2019
package.json Update package.json Jan 18, 2019
settings.json.template initial update Jan 18, 2019

README.md

MNTexplorer, a MNT (v2) Block Explorer - v1.0

The MNT block explorer.

This project is a fork of Iquidus Explorer so massive thanks go out to Luke Williams for his code. Further development was derived from Ciquidus Explorer! Thank you!!!

See it in action

Requires

  • node.js >= 0.10.28
  • mongodb 2.6.x
  • mntd, mnt-cli

Create database

Enter MongoDB cli:

$ mongo

Create databse:

> use explorerdb

Create user with read/write access:

> db.createUser( { user: "mntuser", pwd: "mnt", roles: [ "readWrite" ] } )

*note: If you're using mongo shell 2.4.x, use the following to create your user:

> db.addUser( { user: "mntuser", pwd: "mnt", roles: [ "readWrite"] })

Get the source

git clone https://github.com/risingstar2018/blockexplorer explorer

Install node modules

cd explorer && npm install --production

Configure

cp ./settings.json.template ./settings.json

Make required changes in settings.json

Start Explorer

npm start
OR
forever start bin/cluster

note: mongod must be running to start the explorer

As of version 1.4.0 the explorer defaults to cluster mode, forking an instance of its process to each cpu core. This results in increased performance and stability. Load balancing gets automatically taken care of and any instances that for some reason die, will be restarted automatically. For testing/development (or if you just wish to) a single instance can be launched with

node --stack-size=10000 bin/instance

To stop the cluster you can use

npm stop
OR (use corresponding to above explorer start)
forever stop PID
while you need to search for the correct PID with 'forever list', usually it would be 'forever stop 0' if no other forever processes are running

Syncing databases with the blockchain

sync.js (located in scripts/) is used for updating the local databases. This script must be called from the explorers root directory.

Usage: node scripts/sync.js [database] [mode]

database: (required)
index [mode] Main index: coin info/stats, transactions & addresses
market       Market data: summaries, orderbooks, trade history & chartdata

mode: (required for index database only)
update       Updates index from last sync to current block
check        checks index for (and adds) any missing transactions/addresses
reindex      Clears index then resyncs from genesis to current block

notes:
* 'current block' is the latest created block when script is executed.
* The market database only supports (& defaults to) reindex mode.
* If check mode finds missing data(ignoring new data since last sync),
  index_timeout in settings.json is set too low.

It is recommended to have this script launched via a cronjob at 1+ min intervals.

crontab

Example crontab; update index every minute and market data every 2 minutes

*/1 * * * * cd /path/to/explorer && /usr/bin/nodejs scripts/sync.js index update > /dev/null 2>&1
*/2 * * * * cd /path/to/explorer && /usr/bin/nodejs scripts/sync.js market > /dev/null 2>&1
*/2 * * * * cd /path/to/explorer && /usr/bin/nodejs scripts/masternodes.js > /dev/null 2>&1
*/5 * * * * cd /path/to/explorer && /usr/bin/nodejs scripts/peers.js > /dev/null 2>&1

forcesync.sh and forcesynclatest.sh (located in scripts/) can be used to force the explorer to sync at the specified block heights

Wallet

The wallet connected to Diquidus must be running with atleast the following flags:

-daemon -txindex

Donate

MNT: MVEjiBBL4VUcSxpyCNGuZWbF5FKL2mcYC9
BTC: 3Mv8weG6JkJMRQA6wPf34WJ11sSWw53QZg
ETH: 0xc2e143DF9633078Ba1317d2A60BA14F2F7f284d3

Known Issues

Database Querys are slow. Index are not working correct you need to create the index in the mongodb

db.addresses.ensureIndex({"a_id":1})
db.getCollection('txes').ensureIndex({"txid":1})
db.getCollection('txes').ensureIndex({"timestamp":1})
db.txes.collection.createIndex( { timestamp: -1 } )
db.txes.ensureIndex({"total":1})

script is already running.

If you receive this message when launching the sync script either a) a sync is currently in progress, or b) a previous sync was killed before it completed. If you are certian a sync is not in progress remove the index.pid from the tmp folder in the explorer root directory.

rm tmp/index.pid

exceeding stack size

RangeError: Maximum call stack size exceeded

Nodes default stack size may be too small to index addresses with many tx's. If you experience the above error while running sync.js the stack size needs to be increased.

To determine the default setting run

node --v8-options | grep -B0 -A1 stack_size

To run sync.js with a larger stack size launch with

node --stack-size=[SIZE] scripts/sync.js index update

Where [SIZE] is an integer higher than the default.

note: SIZE will depend on which blockchain you are using, you may need to play around a bit to find an optimal setting

License

Copyright (c) 2018, MNT
Copyright (c) 2017, The Chaincoin Community
Copyright (c) 2015, Iquidus Technology
Copyright (c) 2015, Luke Williams
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

  • Neither the name of Iquidus Technology nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

You can’t perform that action at this time.