# TWINS: Blockchain health check

**1. Check the blockcount from the local wallet perspective:**

![](https://cdn-images-1.medium.com/max/800/0*wtWCbnJZnONFJaXC)

Compare it to the one of the blockchain explorer @ [https://explorer.win.win](https://explorer.win.win/)​![](https://cdn-images-1.medium.com/max/800/0*F9EdcHNf_YsiZDYo)

They must match.

If they don’t match here’s what to do:

\- Go to Tools > Peer list and see if you have peers running version v3.2.0.4 or lower. If you do, ban them as follows:![](https://cdn-images-1.medium.com/max/800/0*Pr1Q6x64tw5XrK-M)

* Once you’ve done that and to avoid them from coming back, you’ll need to do delete the following .dat files peers.dat, banlist.dat, mnpayments.dat in the %appdata%/twins folder:

![](https://cdn-images-1.medium.com/max/800/0*_xl4os1ryYUfy1KB)

* Then do a full resynch by closing and restarting the wallet.

**2. Check the blockcount from the remote wallet perspective:**

For those using the nodemaster script:

*twins-cli -conf=/etc/masternodes/twins\_nX.conf getblockcount*

For normal script:

*./twins-cli getblockcount*

And compare it to what explorer says, if they match your are good. If they don’t you’ll need to to a full resynch of your MN with the TWINS network/blockchain as follows:

A. Delete the blockchain folders called “blocks” and “chainstate”. Located in /var/lib/masternodes/twinsX if you are running the nodemaster script

B. Delete the .dat banlist.dat, mnpayment.dat, peers.dat located in the same folder.

Then do a full a resynch 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 command to stop and restart the twins daemon should be:

./twins-cli stop \
twinsd –daemon

**PS: Another way to verify 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 they match with what the TWINS explorer says.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://achilles1.gitbook.io/workspace/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.