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.
acf5987e922b8a7518cd9ed77578ad354c083c3b9ea9839c43890a8cecf28a21
Both payments are on their chains and locked to the same secret hash 9645b6e6d06eae247ac188314ba6f9848f30b23d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: acf5987e922b8a7518cd9ed77578ad354c083c3b9ea9839c43890a8cecf28a21
- MakerPaymentSpent: fbf6ccb4899a8e7ad5d48250c1886f98cdf78ea6da78bc9ca5ec4d2be26bc299
45b45ebfce84e810f98750a19f6b5f713ce9d0f54bbb00caf004dea8ab19e831
Both payments are on their chains and locked to the same secret hash 9645b6e6d06eae247ac188314ba6f9848f30b23d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ef9fefa8dc69a1782b0655b1077fb3e6e7dc0302036847c9e322f03f0fc105cd
- TakerPaymentSent · TakerPaymentReceived: 45b45ebfce84e810f98750a19f6b5f713ce9d0f54bbb00caf004dea8ab19e831
- TakerPaymentSpent: 5ffc73ac98fb1991f45def062b1b6a078578dd025e5685f080f81e311dd3be58
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.