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.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element)
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.
This payment cannot be read on its chain yet. Checked 2026-10-01 14:00:15 UTC.
14c0d98fa0332557337a2a2ba83d9a71786b7412ae1d87a51f962d0b0c085c6a
SC settles as SIA, whose transfers do not appear as an output any chain server can read, so the transaction the record names cannot be checked against a chain here
- MakerPaymentSent · MakerPaymentReceived: 14c0d98fa0332557337a2a2ba83d9a71786b7412ae1d87a51f962d0b0c085c6a
- MakerPaymentRefunded: ce915d2475fb6108165fc2a409f881a498c2043624f033f593dfdde63dbb62ac
24c0175bce4745d7b58b476feab7f7f76e0eb82d1138b3fb7303deb6c6fc98dd
confirmed on-chain
- TakerFeeSent · TakerFeeValidated: fe3b1629187070045b1dc11f9690a79addc907ae55b576b8abf29b0afc0624da
- TakerPaymentSent · TakerPaymentReceived: 24c0175bce4745d7b58b476feab7f7f76e0eb82d1138b3fb7303deb6c6fc98dd
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.