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.
86c5c2785c88caf4c0fac0f1a6945ec9aa4850001a819562eaeda0deed2e25c8
Both payments are on their chains and locked to the same secret hash 5674ab388bdc337b3f1b861c2fd5da78fb6d262a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 86c5c2785c88caf4c0fac0f1a6945ec9aa4850001a819562eaeda0deed2e25c8
- MakerPaymentSpent: ca75312dddac4139edda7071733cb964656b616a769789d3a2365967a41be511
0acd83d7fc2e354a92f748936c251a7cec7054b2ca4273f443f2d1d1ca0eac03
Both payments are on their chains and locked to the same secret hash 5674ab388bdc337b3f1b861c2fd5da78fb6d262a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3bad343fc8cf3e62f67d44c6f1dc9e2dc8e30932546ca40cb64c6d6a27dffc39
- TakerPaymentSent · TakerPaymentReceived: 0acd83d7fc2e354a92f748936c251a7cec7054b2ca4273f443f2d1d1ca0eac03
- TakerPaymentSpent: a51396b43982b3965773b5fbe6fd7c5afdc9935f3113b5f193b310b3328955fa
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.