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 d9148ed91d27faf86cf7a8ccc807b38d3cfb272c1608c81531e7c91d2e16683b. Checked 2026-11-08 05:54:36 UTC.
7369a6a6b59104fe711620a5d1763af61620269c816f6e61427c74bc8d014149
Both payments are on their chains and locked to the same secret hash 19592fb274ee76b6024a5b9d2af7fb9689229890, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 7369a6a6b59104fe711620a5d1763af61620269c816f6e61427c74bc8d014149
7347d5fcf8d9715ef179b84d3b225681a9b024dff3fed3bc7ac1afc84b75d36e
Both payments are on their chains and locked to the same secret hash 19592fb274ee76b6024a5b9d2af7fb9689229890, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c56cccc89e3fe1dda6e770fe88435dfcf4f8079b16c0aa17c1f6f85ffb132221
- TakerPaymentReceived: 7347d5fcf8d9715ef179b84d3b225681a9b024dff3fed3bc7ac1afc84b75d36e
- TakerPaymentSpent: e0dfaf514bce133d17c9002ceea439524f2402e3493e4e902f121741e0cb4aef
Reported by kdf-statsdb.