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.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 16)
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-09-28 14:32:31 UTC, so the maker can take it back now. Checked 2026-11-06 01:24:25 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.
948f810ea796b8fa8e9c36c1ce39557ea9ad6683bd568c9afba13a6b19d6636d
Both payments are on their chains and locked to the same secret hash 4f8f665c1b62f11b32afc7eb46381ba9441c1d56, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 948f810ea796b8fa8e9c36c1ce39557ea9ad6683bd568c9afba13a6b19d6636d
277ae820c7278fb1932021f9de8e4faaf7ca8b96aa4e9204ca32c7bafb68f025
Both payments are on their chains and locked to the same secret hash 4f8f665c1b62f11b32afc7eb46381ba9441c1d56, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d4f2f44075dd929eaacc018e2ed8de2b342013b080b7d25549fad4762891b35a
- TakerPaymentSent · TakerPaymentReceived: 277ae820c7278fb1932021f9de8e4faaf7ca8b96aa4e9204ca32c7bafb68f025
- TakerPaymentSpent: 9b7e9a1ff70eea6336afe2a544c3534c127363e535c3b52abe3bc9323fdd9576
Reported by kdf-statsdb-8762.