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.
f4d607fb87716e27c7fe069bef57ac3ab54a5f80d5495cb88aa1a32caf6c1dbd
Both payments are on their chains and locked to the same secret hash eb005dbdab0a0bfd845d22ef2e65e771136fd92d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f4d607fb87716e27c7fe069bef57ac3ab54a5f80d5495cb88aa1a32caf6c1dbd
- MakerPaymentSpent: b6d21fa69e4d596b993064ada64789d405e0f57054931b86d0c4016f872c59e2
d48b3ae508920cd5321b3e425ff370bfadb7ca045e13cefdd4b9fb1e2a505196
Both payments are on their chains and locked to the same secret hash eb005dbdab0a0bfd845d22ef2e65e771136fd92d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 780679c1b7a6fdf9cbf474960d54a949b89db1619fe72fbbe902ebf03e6f884f
- TakerPaymentSent · TakerPaymentReceived: d48b3ae508920cd5321b3e425ff370bfadb7ca045e13cefdd4b9fb1e2a505196
- TakerPaymentSpent: adc9d4eb604843eadbaa98eee245be17272b3de73bd9ce6088b8752c828b2b61
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.