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.
396418f992eff23996d5b129c29a1fbe5487f489d35064832e747534c44a2baa
Both payments are on their chains and locked to the same secret hash dd89bcb3e3257fb87a5aec5d6f8da43b52368a6c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 396418f992eff23996d5b129c29a1fbe5487f489d35064832e747534c44a2baa
- MakerPaymentSpent: a70a763993ad3d293c1a5f2ef7ac3445ec9cf7fe5ebbeb1aa25a57a229a11749
ce4c07654312eca49d33f68074fd377e4605b1e4eba49879b483ad80d35bea95
Both payments are on their chains and locked to the same secret hash dd89bcb3e3257fb87a5aec5d6f8da43b52368a6c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d8f8328cc4e992f93c6928048779bb3a1371764a939bdc33997012c6ae7e7cf5
- TakerPaymentSent · TakerPaymentReceived: ce4c07654312eca49d33f68074fd377e4605b1e4eba49879b483ad80d35bea95
- TakerPaymentSpent: 21a8783b711361b2670e81c3da74299d7875d3eedb8955364799d55b3cc1741b
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.