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.
a936d7d11cdf4413b9855b2b8ad94c931cfef102ceb7651531bd3fef15515e1a
Both payments are on their chains and locked to the same secret hash 366425a5374598083bbb2c14bc54f57886df7097, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a936d7d11cdf4413b9855b2b8ad94c931cfef102ceb7651531bd3fef15515e1a
- MakerPaymentSpent: 77e187f3fdc24a0f9ec08373e01d2e1309e802896633205565dcab8b5bfb1dea
5571410572da8af54c27e24991f75870d101a4a6125e80a3754e897978decae9
Both payments are on their chains and locked to the same secret hash 366425a5374598083bbb2c14bc54f57886df7097, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cf35a13fce5b5047df2e60e0a568e02a54642e8dadd7e394a1b78322406746aa
- TakerPaymentSent · TakerPaymentReceived: 5571410572da8af54c27e24991f75870d101a4a6125e80a3754e897978decae9
- TakerPaymentSpent: 9e995cfc8ffbbb2c6549afa28127e81ebc8c5a6cba6f77df55c115304bacf1fb
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.