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.
b47d870b141f43b4bff7dba8860665e20a32ac48f6712e61b02978316f6dac85
Both payments are on their chains and locked to the same secret hash 112c5028a1157698963f001f1144bac44d0759f6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b47d870b141f43b4bff7dba8860665e20a32ac48f6712e61b02978316f6dac85
- MakerPaymentSpent: 1159f61d2995eeaf1dc76e652d3a55e7384b83e1ed20460d60c1bf5eba2053fd
89dc127224b9d190e43bd7c988fa3267afab37785071cc646830629e742c6226
Both payments are on their chains and locked to the same secret hash 112c5028a1157698963f001f1144bac44d0759f6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5de31bcf8a68930a00ed7a1148e3f5367a641c43ef0952293d54c92e8923626f
- TakerPaymentSent · TakerPaymentReceived: 89dc127224b9d190e43bd7c988fa3267afab37785071cc646830629e742c6226
- TakerPaymentSpent: 59cd747568c287780d61e0a4fbb5bb6be81fcbb29e66e7da0f03381ccaa2903a
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.