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.
27b5acf625a6f09d0c0024abe11de03f45433ceb8e6d97363e1cd0323f9750bb
Both payments are on their chains and locked to the same secret hash f75f10b80df8a3d1e8bf928bc93ee320c7b1bad0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 27b5acf625a6f09d0c0024abe11de03f45433ceb8e6d97363e1cd0323f9750bb
- MakerPaymentSpent: a9e93706551ec7c4f3bd535066b8dc1661d0756eba9a8514fc2982f0b18ee53a
e0a6fa4a8a155098c25c6316e1ca4f24edf661d6d41945dbcba7998ddc68064e
Both payments are on their chains and locked to the same secret hash f75f10b80df8a3d1e8bf928bc93ee320c7b1bad0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f77fe265776fed7191d15905cbf4e7c57a9c13f0bb17c89cf6dd295f7061b79b
- TakerPaymentSent · TakerPaymentReceived: e0a6fa4a8a155098c25c6316e1ca4f24edf661d6d41945dbcba7998ddc68064e
- TakerPaymentSpent: 6b31dd3439157590b9e98459ed02e4b1ef4f54b89a3c21e80232a501fd2078f0
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.