This one took about 2.0× the usual for LCC/DGB. 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.
c060160a4bbc51e65caaec02fc06d5070fca852c8553f00d1b114de2b62b3570
Both payments are on their chains and locked to the same secret hash a6eb7f1075a9c8218fc5885cd92d7612e4e3b2f6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c060160a4bbc51e65caaec02fc06d5070fca852c8553f00d1b114de2b62b3570
93f7ffbcc9e89bebe07afce46ffd58adc8b6d746343e90f96322bd8fb393f984
Both payments are on their chains and locked to the same secret hash a6eb7f1075a9c8218fc5885cd92d7612e4e3b2f6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: d9d1852f5a4770580fa78c490669b03fcbdc05abd7faeafe9cd18e9d4f7c15c9
- TakerPaymentReceived: 93f7ffbcc9e89bebe07afce46ffd58adc8b6d746343e90f96322bd8fb393f984
- TakerPaymentSpent: de2795be9b9f1a217f21ef4aeaa4f2ead9c8a4e09c08fd9bec0182f21241bdd9
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.