o_e_l_e_o, you are exactly right. I could have made that clearer. The two inputs for the consolidation transaction in question were from the same address. That said, I'm not sure I understand your explanation. Why wouldn't Core scan the address that the two transactions were consolidated to?
If the address isn't in the wallet in Core, then Core won't scan it. The usual explanation for this is that it is beyond the "gap limit". Given that it is possible to generate billions upon billions of individual addresses from one set of extended keys, wallets cannot possible scan them all. So they will usually scan the first handful and stop, unless you specifically tell the wallet to scan for more.So it all comes down to exactly how you have set things up. Did the consolidation transaction send coins to an address in the same Sparrow wallet, or to a new wallet? Is the wallet you have open in Core simply the one that Sparrow creates automatically, or have you created it yourself by importing keys or descriptors?
