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.
ebc8c8f20219e868a325d75d5f30ad6114f6768a3ca937d18e9d5a4bb0ee4106
Both payments are on their chains and locked to the same secret hash e6980b90bab0d5a6d45d8a8ce7c79c67015f225a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ebc8c8f20219e868a325d75d5f30ad6114f6768a3ca937d18e9d5a4bb0ee4106
- MakerPaymentSpent: 7c9aa5796d02e30e96a8620211e6331e3ce1e22f3af0f8db39abaa4719aa61e2
ca7197c848ed9d58fa7111b633f09e845558273d49241a11918272d0965654bb
Both payments are on their chains and locked to the same secret hash e6980b90bab0d5a6d45d8a8ce7c79c67015f225a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 60d26127fa16343d164bac51fa21f78853f64dd0575e99a9781322cd27f54b01
- TakerPaymentSent · TakerPaymentReceived: ca7197c848ed9d58fa7111b633f09e845558273d49241a11918272d0965654bb
- TakerPaymentSpent: 109cedcfccfdead385ce008af93cf9e54afb24173cc733bf92495e26ce23b85d
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.