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.
2384915bb72485ad83883db8357aede271ceff979de6392f86208d18f61df57b
Both payments are on their chains and locked to the same secret hash ef3e9d04f21979a166d06fb55ee29c7eac5d2803, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2384915bb72485ad83883db8357aede271ceff979de6392f86208d18f61df57b
- MakerPaymentSpent: f14ad13dfa3b7b5d087a09cd5714c88120780fbb4cc3f177ab4004c68cac74e5
971a9e186de9836c4b8c7741ec3898356a9bcb7f430624412f9962dae7ca4248
Both payments are on their chains and locked to the same secret hash ef3e9d04f21979a166d06fb55ee29c7eac5d2803, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3caa8b78a2e80a55a7ac530c6ca603ce648193faa30b893adebeccba0d77d704
- TakerPaymentSent · TakerPaymentReceived: 971a9e186de9836c4b8c7741ec3898356a9bcb7f430624412f9962dae7ca4248
- TakerPaymentSpent: 6114cec28cc7480eca54bf5a7d29314b127f9c90066997c54adb82a0e66db63a
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.