This one took about 2.3× the usual for LBC/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.
ccfa4a0a0899b183460ed0e6b26fb509ab9a24bf2e0a25c6b96d4f32b8cedd86
Both payments are on their chains and locked to the same secret hash 35f1695cfb5bb429ca5ff38b48225f84ca3caff7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: ccfa4a0a0899b183460ed0e6b26fb509ab9a24bf2e0a25c6b96d4f32b8cedd86
101ad2eae32099ed2fc22fa03169dfbd3ee2236fbbc9c83f4788f6e20ad537a4
Both payments are on their chains and locked to the same secret hash 35f1695cfb5bb429ca5ff38b48225f84ca3caff7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 65b53b3aaacef43f4d0f58eb3a729cf1be4e2f230c26b8a365c301aceccc363d
- TakerPaymentReceived: 101ad2eae32099ed2fc22fa03169dfbd3ee2236fbbc9c83f4788f6e20ad537a4
- TakerPaymentSpent: eb3b0687d36110d540a07072544617b1e2f40f977806b5be4db8f75568dd9c68
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.