This one took about 4.4× the usual for LBC/DOGE. 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.
48349849553161fff2b3460670c60b58b9c953dace0ed1d018c7a6b6742ba33f
Both payments are on their chains and locked to the same secret hash 3f782e1429c7606a4456ddc70143f3575ae1d095, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 48349849553161fff2b3460670c60b58b9c953dace0ed1d018c7a6b6742ba33f
bf74610d8ab3ec98b1e8c713b16fb8e8b656d478432e970b952927e6daeb492f
Both payments are on their chains and locked to the same secret hash 3f782e1429c7606a4456ddc70143f3575ae1d095, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: b263618535e684e0b612377c6ec241feba90c0b3c8a84aa6ae750a0478b392f0
- TakerPaymentReceived: bf74610d8ab3ec98b1e8c713b16fb8e8b656d478432e970b952927e6daeb492f
- TakerPaymentSpent: 467dd4079df7d2e9db0d35af0d06a392108a927ae3eb4f94708114108a6c8ffd
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 kdf-statsdb.