This one took about 2.2× the usual for VTC/LTC. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
c881ee94473b180f96a401140900cdebccb267c04e6200de7a2c3ec93921ff09
Both payments are on their chains and locked to the same secret hash 866a17cc0dfda1f2928842f00393d244a56739e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c881ee94473b180f96a401140900cdebccb267c04e6200de7a2c3ec93921ff09
f406de544e8e62f0fe21590aaeee5273656936ebb016f490cc897179fcc78500
Both payments are on their chains and locked to the same secret hash 866a17cc0dfda1f2928842f00393d244a56739e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 621987ae3d45e51a5b9ec35f4a80d3910af526ad4c509fdbfffdeb1fa980e5d8
- TakerPaymentReceived: f406de544e8e62f0fe21590aaeee5273656936ebb016f490cc897179fcc78500
- TakerPaymentSpent: bc079a4f5e34d4b95cd0d1d702840485658b1e79fc367233ad152251802fc51f
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by defistats-gleec.