This one took about 2.4× the usual for VTC/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.
eec2b3240cd2ceb8ae1223729550f898cf8b75b3f4a833597ee349b7cff32f74
Both payments are on their chains and locked to the same secret hash 1073799919a243fd06bff1bd75dad657d877f9b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: eec2b3240cd2ceb8ae1223729550f898cf8b75b3f4a833597ee349b7cff32f74
eb3165d1e0265ecd430ced01211cf72e8772917d2461753e724754f7a67dcf3d
Both payments are on their chains and locked to the same secret hash 1073799919a243fd06bff1bd75dad657d877f9b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: f0f7bc9feb95672e0c74cc018e894b89459387e2c8d5f80dcbf6b1b2a888c27f
- TakerPaymentReceived: eb3165d1e0265ecd430ced01211cf72e8772917d2461753e724754f7a67dcf3d
- TakerPaymentSpent: 901078a3d93e391e643f293ca969b169b2fc60c7df8f4271a2c101ef5eaf4cbd
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.