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.
84a2bc8e0d80de20058bf3ac1a9521906fabb80daeaa86f33dcd1d3a03e26a31
Both payments are on their chains and locked to the same secret hash 5798b13c15b84c8421e834e216a646ff62382dde, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 84a2bc8e0d80de20058bf3ac1a9521906fabb80daeaa86f33dcd1d3a03e26a31
- MakerPaymentSpent: 248e36c1f34d7e82aa072558e563ef9425ecb8000d698f96a4882f4d2c3aa288
9b8e47eebf94d845a260ec1e976af8ea30a62e1dc9e4b3d978761a914ef9d754
Both payments are on their chains and locked to the same secret hash 5798b13c15b84c8421e834e216a646ff62382dde, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5d6ddc1d8aad90ae3103100aa784d7382f84f6ba3dbbf3e2d0efa2616b4ddc77
- TakerPaymentSent · TakerPaymentReceived: 9b8e47eebf94d845a260ec1e976af8ea30a62e1dc9e4b3d978761a914ef9d754
- TakerPaymentSpent: af7c8dbf9da7011362e799bfc77a26b303e6a2ef75c80505e0ea1b6a59f0bd91
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.