This one took about 2.7× the usual for BTCZ/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.
c0024e523128e3f8558b5f8ec32ecd7fc5a3a0e3bef81ca99d377471f64fd9b3
Both payments are on their chains and locked to the same secret hash e03b109c4a16cb0fc4be4b802d2854d9cd9c3e15, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c0024e523128e3f8558b5f8ec32ecd7fc5a3a0e3bef81ca99d377471f64fd9b3
3dfcfcfb90c93860e72b6496e18594798f43cd4f413538357213c9172e449b29
Both payments are on their chains and locked to the same secret hash e03b109c4a16cb0fc4be4b802d2854d9cd9c3e15, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 34b7855ad7932adf707500cc1b8a0ec151fb68379c8573e1c8dacfd064b8e039
- TakerPaymentReceived: 3dfcfcfb90c93860e72b6496e18594798f43cd4f413538357213c9172e449b29
- TakerPaymentSpent: 85879afd457f074f57f321067834e7bbb5c4ec62bcf7b3b53ddab1b93c46f10a
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 kdf-statsdb.