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.
f5f96840e0720cd89cffaa83d60818eb9a85087895207d129aba2397a9b3c92b
Both payments are on their chains and locked to the same secret hash f086b6253d1519528e6c98014603633aa7d8063b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f5f96840e0720cd89cffaa83d60818eb9a85087895207d129aba2397a9b3c92b
- MakerPaymentSpent: 04ad17cb48396e90244c5aee29b13c72fae50722c83a60a9a069ae6d6fa7d2fb
6c2173cdd36d54a421974749cfa2732a8f821ede047e3bdc1f20f665f56e7756
Both payments are on their chains and locked to the same secret hash f086b6253d1519528e6c98014603633aa7d8063b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 202f9345f8a2e4477fca98ee7a4f91035126e36f697ce18ac5c18610282e4973
- TakerPaymentSent · TakerPaymentReceived: 6c2173cdd36d54a421974749cfa2732a8f821ede047e3bdc1f20f665f56e7756
- TakerPaymentSpent: 8e22a3f22aca44ab84591270bd2084d89a450949a5e48d76a8334e7bf1199eb5
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.