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.
1523fbc904c5938e5d6fd1d994f46128f76b56f45e23f2b002a69fedb114243e
Both payments are on their chains and locked to the same secret hash b31f5b90ea6caf713fe54c16d4039abab4a875d5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1523fbc904c5938e5d6fd1d994f46128f76b56f45e23f2b002a69fedb114243e
- MakerPaymentSpent: 552ea26f39591292229538c9c81b848b646453c9da261daef4ee66f9cfc86c4f
439196fe8b35759a7288aabb1d0fa48d922003d63e9b74011c737211a3a1292b
Both payments are on their chains and locked to the same secret hash b31f5b90ea6caf713fe54c16d4039abab4a875d5, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentSent · TakerPaymentReceived: 439196fe8b35759a7288aabb1d0fa48d922003d63e9b74011c737211a3a1292b
- TakerPaymentSpent: 8a66a725662942eb684f588eb7879c1decaa7de0862d336595a046b8b69463b6
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.