This one took about 2.2× the usual for LCC/QTUM. 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.
a916d92d1e831047b35ca7673d1896ba44f96b8c59a693b036801e725c181a67
Both payments are on their chains and locked to the same secret hash 2f2320de7a87d03af23f23c4edc0c5cd9780f106, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: a916d92d1e831047b35ca7673d1896ba44f96b8c59a693b036801e725c181a67
19a9a9cedfd7539f269698185066c0597f2ab0031c44fb417ed82fd7be2b0ca0
Both payments are on their chains and locked to the same secret hash 2f2320de7a87d03af23f23c4edc0c5cd9780f106, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 543ebbe625ba114046d61889a959f1e4674db6a9a3c6469e5c2fb913143a5ebe
- TakerPaymentReceived: 19a9a9cedfd7539f269698185066c0597f2ab0031c44fb417ed82fd7be2b0ca0
- TakerPaymentSpent: 69991795e8d4f47ea7df75e4edf46d2281d4adcf584a9a2d12b6212ebcbf94a2
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.