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 while the timelock holds.
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 be retried for as long as the timelock holds, and whether it was 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 maker can take it back after the timelock. Checked 2026-09-22 15:46:17 UTC. It will be asked again.
7c796b991242628123f7673410d9f78079abad94cd7b89e294fecacb4656e9ed
Both payments are on their chains and locked to the same secret hash 8ea7ec5a48f6129d88071691e87b2a6da36821a7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 7c796b991242628123f7673410d9f78079abad94cd7b89e294fecacb4656e9ed
9e9e6a371a3750aafb4e9e7119c0817d4d35a595f32ea057c617d34b5fc63561
Both payments are on their chains and locked to the same secret hash 8ea7ec5a48f6129d88071691e87b2a6da36821a7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 0bb5008998882a555bbbca08f49acba33792181746f4db6b917c70e1e89b151b
- TakerPaymentReceived · 9e9e6a371a3750aafb4e9e7119c0817d4d35a595f32ea057c617d34b5fc63561
- TakerPaymentSpent · 60be1613d92beb52c3ba3fa1441e6630658d679737a0ab2363afae3485454c52
Reported by defistats-gleec.