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.
93d29ffbebabe2abd401c3c7f655e4977948875af5ef918cc4be05a2f5bc13db
Both payments are on their chains and locked to the same secret hash b575aa68655f33c565816a39ecdd394c06f7304f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 93d29ffbebabe2abd401c3c7f655e4977948875af5ef918cc4be05a2f5bc13db
125b8e701400ff139073b0ac9ede45f56757bdcafb38944bc8fffb50b7a67353
Both payments are on their chains and locked to the same secret hash b575aa68655f33c565816a39ecdd394c06f7304f, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentReceived: 125b8e701400ff139073b0ac9ede45f56757bdcafb38944bc8fffb50b7a67353
- TakerPaymentSpent: 75925fdf9591da86253952e4602d8b06a365fd084edb89e77aeeff887c433ac6
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.