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:1915] utxo_common:1904] HTLC spend fee 27698752 is greater than transaction output 15336602
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:15: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.
1845d9ac47495e57fe76346ebb9bbdc83d8e974099ab3f181f2e3294a9e7bcda
Both payments are on their chains and locked to the same secret hash d9d703a03f72195e3208005e53dd02ff7eba7ac4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1845d9ac47495e57fe76346ebb9bbdc83d8e974099ab3f181f2e3294a9e7bcda
4fe99f2800175f2dacd43dde74f6da8459dfcb07867e3cf01fdc097e8fd7e7b4
Both payments are on their chains and locked to the same secret hash d9d703a03f72195e3208005e53dd02ff7eba7ac4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d820f64486dd3251db9334291c25600fb8eb24ed77c5197c9af6933bc5aeefd3
- TakerPaymentSent · TakerPaymentReceived: 4fe99f2800175f2dacd43dde74f6da8459dfcb07867e3cf01fdc097e8fd7e7b4
- TakerPaymentSpent: 612385d95b045efb1786403d313c8d8dba6675da977d866aafb269bc35286e3a
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.