This one took about 140.3× the usual for KMD/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.
The record stops at MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
the transaction was rejected by network rules. 16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried is a question for the chain rather than for this log.
The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the timelock expired 2025-12-19 11:44:22 UTC, so the maker can take it back now. Checked 2026-11-06 04:47:03 UTC. It will be asked again.
Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.
1199cae2285646cb7440aece60fcc45e933394e74e77468c5fb3ceead0272a33
Both payments are on their chains and locked to the same secret hash 3a2ab79393b057ecf7c68d224b5648392d7a4df2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1199cae2285646cb7440aece60fcc45e933394e74e77468c5fb3ceead0272a33
e8aff8f85f0a1aaf78d6dd3cf523e0dc037ab8bb4f10b71ade7fdcbd3f11ba49
Both payments are on their chains and locked to the same secret hash 3a2ab79393b057ecf7c68d224b5648392d7a4df2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e5a2b64a3e1e55e25a793343f3d2bbbdb3d91a54c0bb07fa97a365507a006958
- TakerPaymentSent · TakerPaymentReceived: e8aff8f85f0a1aaf78d6dd3cf523e0dc037ab8bb4f10b71ade7fdcbd3f11ba49
- TakerPaymentSpent: 61a81ac9cbb5ba79e1e5966843e67e26ee7ea2601d072f0334f6001c74cb20ad
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.