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 7c12e7ff1de4c2a4d90cd20768613ca4b2941aa83ff0da1a9ff32b5db5df0b83. Checked 2026-11-02 10:42:58 UTC.
6fee25c634b853a30cf0109037b6bb08409a3828b8cc3a8483bf21c6903ac988
Both payments are on their chains and locked to the same secret hash df12a49abc44bb791ef27fcce3ad2e8da6b8a031, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6fee25c634b853a30cf0109037b6bb08409a3828b8cc3a8483bf21c6903ac988
acfc7e7058f07694b0cf184c2e21d3ab1375a9541c5ec9c4d431527ef8925f70
Both payments are on their chains and locked to the same secret hash df12a49abc44bb791ef27fcce3ad2e8da6b8a031, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d9e7efb024115f274bcc7d9ec578209773821ed0fdef41870703938a3128e341
- TakerPaymentSent · TakerPaymentReceived: acfc7e7058f07694b0cf184c2e21d3ab1375a9541c5ec9c4d431527ef8925f70
- TakerPaymentSpent: ab52c986275f9ac48aaf86e01bbd7093fe72fca9334fa803317bccd17920c1df
Reported by kdf-statsdb.