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.
9b308e9c0202db7e7f0b6291ec186363a736f00a58735a0b007e7836650e586d
Both payments are on their chains and locked to the same secret hash 115139efd2552dd3951e11b71f09d1b888dfa49a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9b308e9c0202db7e7f0b6291ec186363a736f00a58735a0b007e7836650e586d
- MakerPaymentSpent: d0f25b6e2e1916febdd0d64048301910861623ae30ed53b53749dda3c6ae7d2e
de3f3630b0b86e52431193c9620825116d0113112ea51803e1397b70186ddd94
Both payments are on their chains and locked to the same secret hash 115139efd2552dd3951e11b71f09d1b888dfa49a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0ac11e33d8a56f46bd72b8d726277e340efcdd485770b70d3a369379a80842b5
- TakerPaymentSent · TakerPaymentReceived: de3f3630b0b86e52431193c9620825116d0113112ea51803e1397b70186ddd94
- TakerPaymentSpent: d06fdc6a16189e48a12367962b9490f040385c92202e19574847eacafd2b7555
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.