Same chain, to my knowledge. Perhaps that pool went on a fork?
Share the TXID's in question and maybe we can assist.
Here's a small subset of the transactions I don't see on the chain. The client just returns "Invalid or non-wallet transaction id"
Date (EDT) Destination address Amount Txid
1-May-17 2:34:19 AM RN3EcJ8PB6Ci9qjPnTUM1yPELd8AodPdnP 106925.4563 9dabdff91b362317bce149642f2a7988d4e1b650e4af12b51a71f756127def08
1-May-17 2:34:20 AM RYLyovgbxorkmVRzFNXWzt8PKLN9N4fURP 131172.6599 2280e1ff0de1dfea388618c1afcebffc22a9c9ff85c876b8e449205db3db1924
1-May-17 2:34:21 AM RBP4LUpAj39xb7T5JEK2ML4hMRfnLJ7uw3 252226 967a2dc8594f78d16a6adcf7068554744df24a11cb7b70d0a3974c22da2f3648
1-May-17 2:34:22 AM RDtBg3WmPzqcjjGiT3AoCmicfpPE4qgcFu 447397.3222 72476fbc6e623a1aa214926d5b356996ddc0b75d15a3e294d2fe56946bf725d1
1-May-17 2:34:23 AM RLpxahx4hUNd1xVgARNwuUn6DWYVGatQ2w 781039.3804 8e9d66b4d4299fd1f5c24e5767a6ed8b45c7662cb832768c8270b5c974651d40
I appreciate any insight you can provide
All these appear to be sent around the same time, second apart. Was this automated?
I suspect a fork occurred around that time and orphaned these txs. Do you have control of the sending wallet? Move the input address private key to a clean wallet and -rescan.
Such a small amount compared to the balance on those addresses ... Hats off to the early adopter. Congrats to you sir.
NYC wallets also have the config option to spend unconfirmed change. If that was enabled and these tx really were sent 1 second apart .... any failure of a single tx would cause problems for the next that included the unconfirmed change. And the next, and the next. The option is in the options under the wallet tab.