This one took about 3.5× 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.
ff02bdb2940da9859792c25d27fe52b77206521a65684f8f03174e669453b0f0
Both payments are on their chains and locked to the same secret hash b24af7f0d12fc19765fc0df814b47d90f3e3542b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: ff02bdb2940da9859792c25d27fe52b77206521a65684f8f03174e669453b0f0
f9215632c1a0da81885ba756de2686d2f7b573fef1dedaf7e01890b75247c6dc
Both payments are on their chains and locked to the same secret hash b24af7f0d12fc19765fc0df814b47d90f3e3542b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 83940b1bc04ac3b73f2f7a0d5ebdede12990d83529ee80e0f5c9fbc45738f77c
- TakerPaymentReceived: f9215632c1a0da81885ba756de2686d2f7b573fef1dedaf7e01890b75247c6dc
- TakerPaymentSpent: 16b0e7a2df13975a95357f5822976fb3d12942b57014a84f60c3e052083fb9a2
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.