I find this useful article during 7 waiting days to get my first payment for Monoeci.
it's a really good checklist that can be apply to every masternode.
Reference from Jakiman
Although the Masternode Management Panel was added from PIVX Qt Wallet v22.214.171.124 onwards, it is still sometimes good to know the more in-depth check methods. So here is a list I made that covers most of the key checks that can be done to ensure your controller wallet and remote masternode is working well and will receive payments in due time. (a brand new masternode may take up to 4-5 days for its first payment)
The commands can be run from the debug console or at a command line depending on the wallet and OS.
You may need to add "./pivx-cli" (actual path may vary) in front of the mentioned command on linux.
- Check "masternode list-conf" from controller wallet. Ensure the status of the masternode says Enabled. What this means is that your TXID is still listed on the masternode payment list.(masternode list)
- Check "masternode list-conf" from controller wallet. Ensure the IP address matches up with your masternode's IP address.
- Check "masternode status" from masternode wallet. Ensure it says "Masternode successfully started".
- Check "masternode status" from masternode wallet. Ensure the IP address is matches up to the one in your controller wallet's masternode.conf for that MN instance
- Check "masternode status" from masternode wallet. Ensure TXID matches the one in your controller wallet's masternode.conf TXID for that MN instance. (or txHash from masternode list-conf)
- Check "masternode status" from masternode wallet. Ensure Pubkey matches the corresponding receiving address with the 10K PIV for that MN instance.
- Check masternode's pivx.conf file. Ensure the privkey in the pivx.conf file matches the one in the masternode.conf of the controller wallet for that MN instance.
Although I assume it is, the privkey mentioned above needs to be the one generated via "masternode genkey" from your controller wallet.
- Check "masternode list" output from both your masternode & controller. Just confirm that the last TXID matches up to ensure they are same.
- Check "masternode list" output from both your controller. Either find (or grep) the output and see if your masternode's TXID is listed.