That is in the normal range for BTCZ/LTC. The time a swap takes is set mostly by the block spacing of the two chains involved, so a pair with slow blocks is slow for everyone, every time.
d0cb060c0f6b69596805e8865b3260646f3a79f15cd9c923f5bf1b8a7b8bdc61
Both payments are on their chains and locked to the same secret hash ab5ba5a883aaaefd39de4f93cec5b71495ad6e1a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: d0cb060c0f6b69596805e8865b3260646f3a79f15cd9c923f5bf1b8a7b8bdc61
85609bcd2df158cd5e528b318ff6cfa26d3f49b4446a64309b4e5bbebf52326b
Both payments are on their chains and locked to the same secret hash ab5ba5a883aaaefd39de4f93cec5b71495ad6e1a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: fd5723613d5fa37f7b21125211bca1d0dd1826b6e069381ced4d9c51a146675c
- TakerPaymentReceived: 85609bcd2df158cd5e528b318ff6cfa26d3f49b4446a64309b4e5bbebf52326b
- TakerPaymentSpent: f9d0b9bb93a3660d65e8552f7974dc690e6bfa8695a72204c3bdb32529ba7dbc
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.