This one took about 2.9× the usual for ARRR/LTC. 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.
9a04b7984ce41703fb8f1dea3897ce1a84c2d2a63a5bcc61d23231f6571b0706
Both payments are on their chains and locked to the same secret hash d32bf9d190d8f6d4e82c45798ba7093aff3508e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 9a04b7984ce41703fb8f1dea3897ce1a84c2d2a63a5bcc61d23231f6571b0706
4bd1a838ef2cbfe051918f01c2cd2c9220a69e77a903576be0cad73fac4cdff3
Both payments are on their chains and locked to the same secret hash d32bf9d190d8f6d4e82c45798ba7093aff3508e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 4e256df09f882aee4bffde5d4edf0bce7cc927a928c756c91eb5652e16ba986a
- TakerPaymentReceived · 4bd1a838ef2cbfe051918f01c2cd2c9220a69e77a903576be0cad73fac4cdff3
- TakerPaymentSpent · 3466444d4960f30accdd76dc519f66f8806a006ad67e70472196dffbfbc08522
No anomalies were recorded against this swap.
Reported by defistats-gleec.