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.
84fee18101366e9bf673352e3b2e4dc3ba4854c5176f75c93cb3f3d254176a52
Both payments are on their chains and locked to the same secret hash 8a086f4dc9e7221eaec73040eab3f3f3baf9fc9b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 84fee18101366e9bf673352e3b2e4dc3ba4854c5176f75c93cb3f3d254176a52
- MakerPaymentSpent: dc719f9565ba8feeb592518309d52af6e2e4bdd6d9c93235abfa2fe6fc452f70
d36ddda30e3c35c17bfe0f9e9b44886a33f6361d34f5d8195e76ef9f783c3072
Both payments are on their chains and locked to the same secret hash 8a086f4dc9e7221eaec73040eab3f3f3baf9fc9b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c26b5f8da04ca69ee6668ef5d09f254f2fce1a469fb8caccf1a827426c935ae6
- TakerPaymentSent · TakerPaymentReceived: d36ddda30e3c35c17bfe0f9e9b44886a33f6361d34f5d8195e76ef9f783c3072
- TakerPaymentSpent: d7b2d93fa1d0d994c66b5cf00edf3dd65ef86eb813687907c2eb9885b00650d9
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.