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 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:2002] "utxo_common:998] utxo_common:950] client:1120] : failed to parse list of 11 headers (coin=MEWC, from=1705125, 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 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-10 06:45:08 UTC, so the maker can take it back now. Checked 2026-11-16 06:47:31 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.
7963ee0ab28b7ee16b9947425e292c70a55c7e35f8ab251b51d8a08c82b4de75
Both payments are on their chains and locked to the same secret hash 74814967ffc503c1f737c7040e588c47030eebc1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 7963ee0ab28b7ee16b9947425e292c70a55c7e35f8ab251b51d8a08c82b4de75
99c07fec916991c0590a52a341d7216e427d82558921b962d64b4ba9ea05f36e
Both payments are on their chains and locked to the same secret hash 74814967ffc503c1f737c7040e588c47030eebc1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9dadd7e33a5346c7540e5609c23bc1a0041537e1860b02c10d16249444f3dbb9
- TakerPaymentSent · TakerPaymentReceived: 99c07fec916991c0590a52a341d7216e427d82558921b962d64b4ba9ea05f36e
- TakerPaymentSpent: 3822f297615ca18779f0f5b5e1763966e8434b9d236292efdd8e75f2bfb96d97
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.