This one took about 2.9× the usual for BTCZ/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.
0b1d3b7843dd2a9f9a2241a97b893396f3c029323f1da6349e87515224eb5726
Both payments are on their chains and locked to the same secret hash f78dfd42bac46e4fdda3b165c6f00a5d216770f5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 0b1d3b7843dd2a9f9a2241a97b893396f3c029323f1da6349e87515224eb5726
b3dfa24387e9c1d56101a41076a9ef09715c97754102db367c777eb342f5d8fe
Both payments are on their chains and locked to the same secret hash f78dfd42bac46e4fdda3b165c6f00a5d216770f5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6253ab63dbb3f2f80fafc8b5d10f05af30af461ea6ec1c11f5d36b00a426e839
- TakerPaymentReceived: b3dfa24387e9c1d56101a41076a9ef09715c97754102db367c777eb342f5d8fe
- TakerPaymentSpent: 9f7bff8495a18a8d233b720b50aadc2514818d1ec78341504eb3a363ecf07bc1
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.