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.
86b32902d0e33ea5f8fb6f8460e4a05af40c55fdfb57ddf12178a6d7c5c4c23c
Both payments are on their chains and locked to the same secret hash 92ba2948f8fb874218815d3bcc15713de91cf4a1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 86b32902d0e33ea5f8fb6f8460e4a05af40c55fdfb57ddf12178a6d7c5c4c23c
- MakerPaymentSpent: b0afa69a7382abf367c0de6d6413bc313a79a86aea54c554ed17092cc443ba16
190a6e9d3e179ea333a3ac05ed94ddc3322de2e2fb5fe75a47134a5baba5b23f
Both payments are on their chains and locked to the same secret hash 92ba2948f8fb874218815d3bcc15713de91cf4a1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5c452710cf06873dd903d325cebe22dd4ab6689a835c2c64e3503acc4dfd4e63
- TakerPaymentSent · TakerPaymentReceived: 190a6e9d3e179ea333a3ac05ed94ddc3322de2e2fb5fe75a47134a5baba5b23f
- TakerPaymentSpent: 8b7d4b6e60f563322a3bc51da848a301dc8c334a637f30c2340bed60687845a5
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.