This one took about 2.0× 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.
b6333ed0251a9b1e3165ced59b7ec7e49d044b5d3a8e4631a957b6c8288ff484
Both payments are on their chains and locked to the same secret hash a2a42e58e94ca1bebd3051eaf84d8dd233b97dba, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: b6333ed0251a9b1e3165ced59b7ec7e49d044b5d3a8e4631a957b6c8288ff484
dc614a03c4fe768f813820cd43b8f42491caa1cfe2b2a798fc705e03ffa3544e
Both payments are on their chains and locked to the same secret hash a2a42e58e94ca1bebd3051eaf84d8dd233b97dba, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 7ff31aa74ac6cf24ccb33be189afc5a0dcf4933d3f0750ae6a924bbdebd5495b
- TakerPaymentReceived: dc614a03c4fe768f813820cd43b8f42491caa1cfe2b2a798fc705e03ffa3544e
- TakerPaymentSpent: 94d0bf895ca8faba5972b458b39e28d172b25369e9008a0d1175061a97106d4d
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.