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.
4ffee9d6b7924879fbad0108cf6c68220a7dd44fff5a44641babde321aa4b93b
Both payments are on their chains and locked to the same secret hash 344d5bab85b61a4a2e74c1c2b6ea0c23fddfaec4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4ffee9d6b7924879fbad0108cf6c68220a7dd44fff5a44641babde321aa4b93b
- MakerPaymentSpent: 4fbe90dde501de8261ef723075e4a86891847f763dd8f4e28bfad11468316a1e
d38a1b373af4b8d2492700e07b3a5f05f0f19e1612c9779b8c8094706b12012a
Both payments are on their chains and locked to the same secret hash 344d5bab85b61a4a2e74c1c2b6ea0c23fddfaec4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b04510eff8b86d4f7f9a0ab4540850968964a37b5728bfddb4925f17862534d2
- TakerPaymentSent · TakerPaymentReceived: d38a1b373af4b8d2492700e07b3a5f05f0f19e1612c9779b8c8094706b12012a
- TakerPaymentSpent: 0d47bfc8b0505a0eb02016611db4aad18f5838e6b0017c3861f1d2917de0c1ad
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.