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.
9c96b2bd2ca8efa0fd5815e42ee8d71c80f891d6fc6dcc49fa294fbe5569c2e8
Both payments are on their chains and locked to the same secret hash 837f4019305d5a63b8a725eb901693b02855678b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 9c96b2bd2ca8efa0fd5815e42ee8d71c80f891d6fc6dcc49fa294fbe5569c2e8
- MakerPaymentSpent: 872ca5527d2a8c33314da4158eadaa8d7ed88dd64feb91432546dd3f14507957
7e77c8fa17df1d6fe7dfcf196d6ee0b6367c8c2117e2a095fe811e043d10c53c
Both payments are on their chains and locked to the same secret hash 837f4019305d5a63b8a725eb901693b02855678b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e0c498cd98359a5d2a9c64649e8a5aa5926679c62f88048a42d774cb432ef287
- TakerPaymentSent · TakerPaymentReceived: 7e77c8fa17df1d6fe7dfcf196d6ee0b6367c8c2117e2a095fe811e043d10c53c
- TakerPaymentSpent: 1a802ec87ecfda31eab4ef4e01e08e4cacdd6bec49f592af1425ed70e43fda5b
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.