That is in the normal range for PIVX/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.
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.
taker_swap:1741] "utxo_common_tx:437] electrum_rpc_client:959] header layout not implemented for chain_variant PIVX"
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 2026-10-26 06:20:19 UTC, so the maker can take it back now. Checked 2026-11-16 03:13:16 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.
caa38412a66121ed60f2f97cd019c80c6d430b54239897ddc6150470229b9575
Both payments are on their chains and locked to the same secret hash 164b24f32af7ec676b469b5a907f794ee4738bbe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: caa38412a66121ed60f2f97cd019c80c6d430b54239897ddc6150470229b9575
04f62a9b546c69227e6e6f4f58709d43cf646efa5203a5c9b30bcefefe136503
Both payments are on their chains and locked to the same secret hash 164b24f32af7ec676b469b5a907f794ee4738bbe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ec035bd394d6dadd0611da19c7e7c7808ed15b3b56ac5853140df4d86b48ab73
- TakerPaymentSent · TakerPaymentReceived: 04f62a9b546c69227e6e6f4f58709d43cf646efa5203a5c9b30bcefefe136503
- TakerPaymentSpent: ccc3f991b881104a89113cae173b3b9d19e07ea24f3218d9bc1b16b2f799e70a
Reported by kdf-statsdb-8762.