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.
4a2ebd2a960a3845a981c8d29dddb005e645309b7914337552f36eca2203dec0
Both payments are on their chains and locked to the same secret hash 8a6f805ab9e9917345a8ba4ea8c4bb688ae122bf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4a2ebd2a960a3845a981c8d29dddb005e645309b7914337552f36eca2203dec0
- MakerPaymentSpent: d70c79ff1ccca830c0f578f0dda81f3ec1fd7cdf79945269413f6e70bca1183f
74718d28aabcbeac5cbbe611a77cbc240bf7eaee728865050799cab0aca8ca02
Both payments are on their chains and locked to the same secret hash 8a6f805ab9e9917345a8ba4ea8c4bb688ae122bf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 17ce89513e2b153ca39e1d5434c938cae6b0b3824dd6ff2c56f184b3265f322a
- TakerPaymentSent · TakerPaymentReceived: 74718d28aabcbeac5cbbe611a77cbc240bf7eaee728865050799cab0aca8ca02
- TakerPaymentSpent: 011776aa5f0188a378d79de2fe8dcad9709ad973d1386ab892b98bf9d6ed7296
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.