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.
330452419184db6e4f2bef9f4cd02d7de344c224d83fce7179de67c363600d13
Both payments are on their chains and locked to the same secret hash 9fb3b4507a35d9bb160098722f0814e4bff04b6c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 330452419184db6e4f2bef9f4cd02d7de344c224d83fce7179de67c363600d13
- MakerPaymentSpent: d3d0574c7c2f44cb0698d74d574513d9826688f5252b237976e60571e52df0f5
96eb8d5ba6a580862b0405136eb6d75c16d2d61f1cef70c6aa4f3fe8e200eaf4
Both payments are on their chains and locked to the same secret hash 9fb3b4507a35d9bb160098722f0814e4bff04b6c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 36f5ac26b385e42613f7b20cb22215a9b79c16f8136be2b3dfcd318726626f3a
- TakerPaymentReceived · TakerPaymentSent: 96eb8d5ba6a580862b0405136eb6d75c16d2d61f1cef70c6aa4f3fe8e200eaf4
- TakerPaymentSpent: e0a6df1437e09f7b5b8e26af0f6b09875f75f2b89242b5e48386c56859049d9c
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.