An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
The record stops at TakerPaymentSpendFailed. The maker's claim on the taker's coin was rejected; it can be retried for as long as that payment is unspent.
maker_swap:1268] !taker_coin.send_maker_spends_taker_payment: "utxo_common:998] utxo_common:950] client:1123] : failed to parse list of 11 headers (coin=MEWC, from=1612295, requested_count=11): UnexpectedEnd"
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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch it. Whether it was retried is a question for the chain rather than for this log.
The chain shows the taker's payment still sitting in its contract: neither claimed nor refunded. The maker never collected, so the secret was not revealed and the taker can take it back after the timelock. Checked 2026-11-16 07:03:29 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.
fdc295a4e0d63b795007d5adc0620a9c1ae092502efce376b6d54fca1c42fa1c
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent: fdc295a4e0d63b795007d5adc0620a9c1ae092502efce376b6d54fca1c42fa1c
- MakerPaymentRefunded: 4cca3650beaee3572f9ef200d0503c94da018bb47bf1bdc00a1ecc786e575c6f
4a6972272f799fdfbadc7eb47df0830b0268a0b58b38e778b149f5b719806c27
confirmed on-chain, locked to this swap's secret hash
- TakerFeeValidated: 57a46fabd761f7c442c6f985195c4152fc16135838ca6905da2c351296c01dd0
- TakerPaymentReceived: 4a6972272f799fdfbadc7eb47df0830b0268a0b58b38e778b149f5b719806c27
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-8762.