This one took about 2.5× the usual for BCH/DASH. 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.
c2db6a0f7eaa39e71fcf4ca5c1e2241caecb69024724042a9e12468e4e536a69
Both payments are on their chains and locked to the same secret hash ddc811f4d3426864aa3d667cd2998284e8a94068, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c2db6a0f7eaa39e71fcf4ca5c1e2241caecb69024724042a9e12468e4e536a69
a3cb646832caf60b73f052e5b19ab2be389122d9f0bd10281c94294f96f07182
Both payments are on their chains and locked to the same secret hash ddc811f4d3426864aa3d667cd2998284e8a94068, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: cd42204b15428016ea5be71b9392b4a90e98ae384ffe75d92f3608ff658a9bb8
- TakerPaymentReceived: a3cb646832caf60b73f052e5b19ab2be389122d9f0bd10281c94294f96f07182
- TakerPaymentSpent: eede73f26469682e0a0f5c37d897c047c05ca318f36f92b1e168e3136c459eba
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.