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.
9e75f3a8838b48efd96dd6fc6dddb782da18077b37d1e6c6f1fbf9704b77aca2
Both payments are on their chains and locked to the same secret hash 36b8e1f27c3bf663104cf9705d093a96425604d3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9e75f3a8838b48efd96dd6fc6dddb782da18077b37d1e6c6f1fbf9704b77aca2
- MakerPaymentSpent: ebab2890923ea23662bed3cee31c36698f787a9ccf17332f147f3218e90239ef
fe3ab21cc61f9067bcf64ed8548b4ac063d7135e8be0c94956ae6af141bb09c2
Both payments are on their chains and locked to the same secret hash 36b8e1f27c3bf663104cf9705d093a96425604d3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f27143f94fde03005c2c15fc91de48ef145d98f348595c069be40b1afc25ba28
- TakerPaymentSent · TakerPaymentReceived: fe3ab21cc61f9067bcf64ed8548b4ac063d7135e8be0c94956ae6af141bb09c2
- TakerPaymentSpent: b464e4937c2b46120bef0f7727344eb629bdd0a8a6f6069f5385763a1fc1828f
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.