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. transaction already in block chain
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 says the claim landed: the payment was spent with the preimage, in ff96d8ad252cb54a74e0276541c0b1eaa2897c02fb884b24b62ecc123da8822c. Checked 2026-09-26 14:14:44 UTC.
2a4ebaea6fbc203b8b87faa1eb5c84dc02e0d9b3b8b9afd668834e95f09877b0
Both payments are on their chains and locked to the same secret hash 65070114b8c5eb9da455761845e9afff4e614ece, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 2a4ebaea6fbc203b8b87faa1eb5c84dc02e0d9b3b8b9afd668834e95f09877b0
82e597a64f2b67d59b02473917b3c74293fba4602c14258fb0016faf56b2a0a9
Both payments are on their chains and locked to the same secret hash 65070114b8c5eb9da455761845e9afff4e614ece, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 3162eec92058e3df01ef645535826126bcd37518d3cdc897f60bd0a1ff40e1b2
- TakerPaymentReceived: 82e597a64f2b67d59b02473917b3c74293fba4602c14258fb0016faf56b2a0a9
- TakerPaymentSpent: 0eae65d9aab43b77bf7931be98c89f965c769a3d4ab8bcb312cde06916526a98
Reported by kdf-statsdb.