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.
3f0780c59e1aa24ecf1f0c5c3fa05a3605789c7e60831001a15dbe685df63d63
Both payments are on their chains and locked to the same secret hash f1cd08965491675b6a9d1f8c404e7f7abe128569, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3f0780c59e1aa24ecf1f0c5c3fa05a3605789c7e60831001a15dbe685df63d63
- MakerPaymentSpent: 201339474cb38c4839306c583e5d8be75a4f7788665466efab813ecc55d7e7fb
144ea95a6a1c4c0ca0f2ef765d573bf95ed147e9f30a920ca9a1406ee055ea6f
Both payments are on their chains and locked to the same secret hash f1cd08965491675b6a9d1f8c404e7f7abe128569, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 6c22050e3e5bd30c94cf4cb4011bc09328e4e441935631570b5fd40d91d89550
- TakerPaymentSent · TakerPaymentReceived: 144ea95a6a1c4c0ca0f2ef765d573bf95ed147e9f30a920ca9a1406ee055ea6f
- TakerPaymentSpent: 6db8dcbef1ebd249fe6b7f554db3ba9c7aab4157d82cc0dcde6b5f559d8367ea
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.