This one took about 3.6× 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.
1483d1cad38cb2a74740f3d687a2fdeb3fe5d7e3d3bd073e77fb20b1ccaba896
Both payments are on their chains and locked to the same secret hash 6e37d6ef479ee11222fecf8d8b2b5ef8ab74e9e7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1483d1cad38cb2a74740f3d687a2fdeb3fe5d7e3d3bd073e77fb20b1ccaba896
e95c3eaf23a6b6a29a6d4fe6edc9442fa13454fcd0b2e3d2fe76cbc4a845f5c5
Both payments are on their chains and locked to the same secret hash 6e37d6ef479ee11222fecf8d8b2b5ef8ab74e9e7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 31a4d411999872dd50e953dd65b5d2a334a6f9a018a948d991dc1a68c30099d1
- TakerPaymentReceived: e95c3eaf23a6b6a29a6d4fe6edc9442fa13454fcd0b2e3d2fe76cbc4a845f5c5
- TakerPaymentSpent: 03c5def92e6823dd758860df2001f1c36ea33e95b850bfff81d4aaf7e51a5c76
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.