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.
9bacdd0653c4ea1fb9572bb963df3e4cf934d2787fd188117713873f567e025b
Both payments are on their chains and locked to the same secret hash 1ec02b10508b6ac0005ee7477652a6ab99010ea5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 9bacdd0653c4ea1fb9572bb963df3e4cf934d2787fd188117713873f567e025b
- MakerPaymentSpent: 1f18159869afb031c83739cf42cd9f375426b37aec16c981edc8ae82c399947e
bb8d1407d85ab41c85a40ee53b2c2f76b48f80f381675866683323ac2f58f0a5
Both payments are on their chains and locked to the same secret hash 1ec02b10508b6ac0005ee7477652a6ab99010ea5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e07d9d96fa4ddc24b491368788571159db0522cf275a2f20e685d6255a77e2e9
- TakerPaymentSent · TakerPaymentReceived: bb8d1407d85ab41c85a40ee53b2c2f76b48f80f381675866683323ac2f58f0a5
- TakerPaymentSpent: c7b7dff93d0772db81d43ee729bd07779a3700edad521318f9b2eba9f260d252
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.