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.
ca36c0800a60b37ddb86e770fe5e30f734a548ed2501542d181399107388f8f9
Both payments are on their chains and locked to the same secret hash 7d98e1ee2936355a37ee316cd7abbb328c790329, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ca36c0800a60b37ddb86e770fe5e30f734a548ed2501542d181399107388f8f9
- MakerPaymentSpent: ebaf4f0ee8b36823e9e0c9238663703037df1da6ff73eef745a4e96f5337e594
05e479aa75d757c082c439e24762ae12322796cbbf6ccc717e7ce517e007691a
Both payments are on their chains and locked to the same secret hash 7d98e1ee2936355a37ee316cd7abbb328c790329, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b1117dacdb90de7ebc73a4dbb84b8f4269aefc97bb1d559e18f1b1cb569fe169
- TakerPaymentSent · TakerPaymentReceived: 05e479aa75d757c082c439e24762ae12322796cbbf6ccc717e7ce517e007691a
- TakerPaymentSpent: 77046fc34072a3ca7464756cceb3e87efd1dcffef0f277cd99d26f26f4b5a256
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.