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.
8bd5aa730a667706ca5b76d628658aff549d6cabb24c69c375fd9c3f37b79ce0
Both payments are on their chains and locked to the same secret hash 454514e338682ea6c7634d5101c58248aceca20b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8bd5aa730a667706ca5b76d628658aff549d6cabb24c69c375fd9c3f37b79ce0
- MakerPaymentSpent: a453113e53df2419370e1bbfae1bbe5007f2a876fd47cc6ff8f8098041fe3f6d
e59c0b38be4ad5ef8c549a2aecbb33da0aecd63fbf5ad32ef11442f10a6ce021
Both payments are on their chains and locked to the same secret hash 454514e338682ea6c7634d5101c58248aceca20b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f49240392671943514b3f5dfd17927a0db78fe9b68a8ff37ecc313e5474b266a
- TakerPaymentSent · TakerPaymentReceived: e59c0b38be4ad5ef8c549a2aecbb33da0aecd63fbf5ad32ef11442f10a6ce021
- TakerPaymentSpent: 9ebd6ad19da1c7688086d53a7cd801000f1252cc1b2db5ed83ce975afa5a84fe
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.