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:1803] mm2src\coins\utxo\ "utxo_common:1186] utxo_common:1139] rpc_clients:2378] 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 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 maker can take it back after the timelock. Checked 2026-11-06 05:45:11 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.
7d9d953fb3f3d3ad299000a1033ff04662161a39114f0ded7b4532ea80dd5c03
Both payments are on their chains and locked to the same secret hash 3e9f280f7ddbe88b9e92426e13c694f84d71f81f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7d9d953fb3f3d3ad299000a1033ff04662161a39114f0ded7b4532ea80dd5c03
b45a77e9e896ebd11fd1152a8d7abe29e38aad838302676b558fec7b3fb48a55
Both payments are on their chains and locked to the same secret hash 3e9f280f7ddbe88b9e92426e13c694f84d71f81f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3df8fb6a0ed83863412b1d316e18555f5ac2351da726f1a0f355623c62f5a2e2
- TakerPaymentSent · TakerPaymentReceived: b45a77e9e896ebd11fd1152a8d7abe29e38aad838302676b558fec7b3fb48a55
- TakerPaymentSpent: 74a5c6e529277fcd8ed579076719f8fb169164d410a94bacd4b084cbb0632313
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.