Blockchain health check
This document explains how to verify that you are on the right blockchain and the solution techniques in case you are not.
1. Check the block count from the local wallet:
Compare it to the one of the blockchain explorer @​
You can also compare it to the second explorer @
The current block must match. If they don’t match, here’s what to do:
  • Check the version of your wallet at Tools > Information and make sure it is the latest one available at
  • Next, close the wallet and delete the following .dat files: peers.dat, banlist.dat, mnpayments.dat.
    • If you are using Windows you will find the files in the "%appdata%/TWINS" folder.
    • If you are using Linux you will find the files in the /YourUserName/.twins folder
    • If you are using a Mac, you will find these files in the /Users/YourUserName/Library/Application Support/TWINS folder
  • Delete the directories blocks and chainstate.
  • Then do a full resync by restarting the wallet.
- The wallet will find new peer connections. Go to Tools > Peers list and see if you have any peers running with an older version. If you do, right-click on them and choose "Ban Node for 1 year":
2. Check the blockcount on your masternode wallets on your VPS (remote wallet):
For those using the Nodemaster script:
twins-cli -conf=/etc/masternodes/twins_nX.conf getblockcount
For the normal script:
./twins-cli getblockcount
And compare it to what explorer says. If they match you are good. If they don’t, you’ll need to do a full resync of your MN with the TWINS blockchain as follows:
If you are using the Nodemaster script:
A. Delete the blockchain folders called “blocks” and “chainstate”. Located in /var/lib/masternodes/twinsX if you are running the nodemaster script (X is the number of your masternode)
B. Delete the .dat files banlist.dat, mnpayment.dat, peers.dat located in the same folder.
Then do a full a resync by stopping and starting the twins daemon:
systemctl daemon-reload systemctl enable twins_nX systemctl restart twins_nX
If you are not running the nodemaster script, the files that must be deleted are located in the /YourUserName/.twins folder and the command to stop and restart the twins daemon should be:
./twins-cli stop ./twinsd or ./twinsd -daemon
Another way to verify that you are on the right chain is to run:
“getblockhash <any_high_block_number>” from the local wallet in debug console and “twins-cli -conf=/etc/masternodes/twins_nX.conf getblockhash <same_high_block_number>” from the MN.
Then see if the hash matches with what the TWINS explorer says.
Copy link