First time this has happened with my nodes, so I thought I’d share.
My masternode received a reward and at the same time, received a second reward which was rejected. Here are the details of the rejected transaction (from QT):
Status: 0/unconfirmed, not in memory pool
Date: 6/14/2020 17:15
Source: Generated
Credit: (not accepted)
Net amount: 0.00000000 SYS
Transaction ID: fc475116282356f8d70c54c9506ab0000361e7a1bbbc0e7f54c1ddfa2d559978
Transaction total size: 205 bytes
Transaction virtual size: 178 bytes
Output index: 1
Generated coins must mature 101 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to “not accepted” and it won’t be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.
Confirmed TXID: c9a75742ae4bc435cb1fb8590d734320ba427fc701e4d2cf9982daf081a5e12b
Selecting ‘Abandon transaction’ in QT then produced an alert on the pc that the transaction on the successful reward was successful, even though it had already produced a successful notification earlier.
Just received a second unconfirmed transaction on another node exhibiting the same behavior:
Unconfirmed TXID: 6d54c672cbe62a83375fb53792325bf5f589726ea98efec9c81038f75f63ec12
Confirmed TXID: 06e5d963c93b2697b0079ee597ba19ac4c211c399ed805d4144a5ca75323207e
Again, two transactions were produced, with one unconfirmed, one confirmed.