This one took about 2.8× 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.
b3c4c118c3190e83f47e44257dfaf09bf3e5a83d26109ccea8fe1ccbdf21ff3f
Both payments are on their chains and locked to the same secret hash 90883e8f508c56204e736a34bf3f2569aa3561b5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: b3c4c118c3190e83f47e44257dfaf09bf3e5a83d26109ccea8fe1ccbdf21ff3f
01f4f90cdae8794e8215aad538ad4827a7ef72ad776cae8c6b6e6837b9c0f8c1
Both payments are on their chains and locked to the same secret hash 90883e8f508c56204e736a34bf3f2569aa3561b5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: a2a60231f00d2b304b227fac1e56d888cf4094eb1739503099515e2a31203c10
- TakerPaymentReceived: 01f4f90cdae8794e8215aad538ad4827a7ef72ad776cae8c6b6e6837b9c0f8c1
- TakerPaymentSpent: c3406831081d87c3a0ddd743e0cb1487a0c13d8ec44e86c6dc3f1e45888fbb59
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.