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.
c843a5a85d07115acb5cb7f5ca2bb0792886060b9917a3d3e2339403e6137835
Both payments are on their chains and locked to the same secret hash 5273ab09359b700326a740fc1a08694a4df5c350, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c843a5a85d07115acb5cb7f5ca2bb0792886060b9917a3d3e2339403e6137835
- MakerPaymentSpent: 1748ce1856f1c298c57a31dd20f15ddf9f41bf16f2d6c42f3c6b16c9e535a4ac
0deddad3467e04685841c79c07258790e064cd84ea6412baf109692c24f57e33
Both payments are on their chains and locked to the same secret hash 5273ab09359b700326a740fc1a08694a4df5c350, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9f0871853ed3f8877abe75b922014fcbbaccc60c2752586ea1568e3fbb27e0e6
- TakerPaymentSent · TakerPaymentReceived: 0deddad3467e04685841c79c07258790e064cd84ea6412baf109692c24f57e33
- TakerPaymentSpent: 435095c61dfa84e860cfc0ad8ab013df330ac56adbdddedc89f9a3389abff58d
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.