This one took about 2.4× the usual for VRSC/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.
5406fc470fc31730f9615c9be645e3d33596511410f0554f7a1c06300d2cfdf2
Both payments are on their chains and locked to the same secret hash b649a52ad414c7bb60036d1fbb7c1ff0df87ab96, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5406fc470fc31730f9615c9be645e3d33596511410f0554f7a1c06300d2cfdf2
0c639a1906657e7b5bd5a3ec55eef5a33c813467ea0667a7e81a179e12779104
Both payments are on their chains and locked to the same secret hash b649a52ad414c7bb60036d1fbb7c1ff0df87ab96, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: a74e83d02db4ce31467eb328a037fd1c3cdec216224d1df0c471ab93e3cfc697
- TakerPaymentReceived: 0c639a1906657e7b5bd5a3ec55eef5a33c813467ea0667a7e81a179e12779104
- TakerPaymentSpent: 58f331f7e3581a0bba6d4c8ba673c2bd6943955f4a0df0022e9123211ff7354e
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.