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.
9f90e2c3de77555acc37dac7aa4b02fb7db6dd50c21e388ab7171696ca5c1d6b
Both payments are on their chains and locked to the same secret hash 13652e10d96f9660de6f6a86fb3ec1529a1e6b21, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9f90e2c3de77555acc37dac7aa4b02fb7db6dd50c21e388ab7171696ca5c1d6b
- MakerPaymentSpent: f1f043294fc0df67d50bc9501cee6951298524f695bf6905030fd92f9dfa967a
e10a157d8a453e23a075ae7a78971dc8df1a804145144fbae32069e2d80ec5b7
Both payments are on their chains and locked to the same secret hash 13652e10d96f9660de6f6a86fb3ec1529a1e6b21, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 727b11ef198538fb050f335ccaed20dc473a8d7e4dcc4111561f0bfc280dce14
- TakerPaymentSent · TakerPaymentReceived: e10a157d8a453e23a075ae7a78971dc8df1a804145144fbae32069e2d80ec5b7
- TakerPaymentSpent: d6093defc557ff3e83386ce9e5e7b1d0d9d4195e1babfd4ac9e7db1fd1ac48ac
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.