This one took about 2.1× 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.
677bf45ced8d48c9719beddd3366ee54b5c18a435ba64188fd8642a8fb7b9cc5
Both payments are on their chains and locked to the same secret hash 387ca05b0df1bb8e3504ec9301593d52413b8080, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 677bf45ced8d48c9719beddd3366ee54b5c18a435ba64188fd8642a8fb7b9cc5
7b41e6f3d1764a4001b759080a40c419652fe4b15cd0fed1e74437ee79574ca1
Both payments are on their chains and locked to the same secret hash 387ca05b0df1bb8e3504ec9301593d52413b8080, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 7ab372d343fb88816677a2c42307e193e679879f0cad7ffcd01016145a2df9d1
- TakerPaymentReceived: 7b41e6f3d1764a4001b759080a40c419652fe4b15cd0fed1e74437ee79574ca1
- TakerPaymentSpent: 9c8f9cd993d5762affe6895de16d9e888e533cbeb87b87bcf877785b1fa661df
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.