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.
6c023089acc67456ceb62a7b624c62c2f0e9db50114750a2075f7a861e30d83c
Both payments are on their chains and locked to the same secret hash c6dffe17f649d168d3bb8a2e8a6c3abd2bbc0fef, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6c023089acc67456ceb62a7b624c62c2f0e9db50114750a2075f7a861e30d83c
- MakerPaymentSpent: d51b974574b7339aa4c96493d4869d3ec57fbc7646b0d9500fe29990dd428feb
682e6d7f6bda29574f1fbea686f2093d346e29dff9719d8757df14255a1b2ae3
Both payments are on their chains and locked to the same secret hash c6dffe17f649d168d3bb8a2e8a6c3abd2bbc0fef, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 294565ac400314f32cb0f1dc1575b9f416be56c7871a68603f53f5386ec1cc2a
- TakerPaymentSent · TakerPaymentReceived: 682e6d7f6bda29574f1fbea686f2093d346e29dff9719d8757df14255a1b2ae3
- TakerPaymentSpent: e3c47d39fa63b5872a6f1036957e9346834c0c560000665a8515d8f887462e7c
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.