This one took about 3.2× 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.
94951f0776068550f02d534320e4d80a2c0f80c5a207a31e483d9550bfdd7f0d
Both payments are on their chains and locked to the same secret hash 8329436d7f34bd014ebc99b01820dad219e5e9da, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 94951f0776068550f02d534320e4d80a2c0f80c5a207a31e483d9550bfdd7f0d
636dd970e38cc4e014e07ef7e900c9e08ec2fdca785e6c94ca7a3f00ea6e6857
Both payments are on their chains and locked to the same secret hash 8329436d7f34bd014ebc99b01820dad219e5e9da, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: f068ffddf0bee3f6d1114082512d04845ea5990b3a441e723dc02bea9ca26db9
- TakerPaymentReceived: 636dd970e38cc4e014e07ef7e900c9e08ec2fdca785e6c94ca7a3f00ea6e6857
- TakerPaymentSpent: fe8d2a79badbb86f5b87065b7e64774edf71b1d08aa884851cf0050c1a1e09dc
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.