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.
7f57829ee1b94654b91cd1ecd51f66143cac8498bd90a74f8cb3703039a16749
Both payments are on their chains and locked to the same secret hash e4bddc2e7263a2a3701b4bee7528dacbc887aaf8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7f57829ee1b94654b91cd1ecd51f66143cac8498bd90a74f8cb3703039a16749
- MakerPaymentSpent: fc1bfb335edf6b8334bb624c864e8534d0642da930baddee73204a87cb84bcee
78cf666afb34df86ea1f35142b456cc3ab59660eef04067ca37cad6d5ff9c132
Both payments are on their chains and locked to the same secret hash e4bddc2e7263a2a3701b4bee7528dacbc887aaf8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0c6b2aff14a5ea49107ab09b0bc9cec29a7060deb9078dd27d96cfa07aaf4b39
- TakerPaymentSent · TakerPaymentReceived: 78cf666afb34df86ea1f35142b456cc3ab59660eef04067ca37cad6d5ff9c132
- TakerPaymentSpent: c836a2be4529e9954e366cbc7b9a49518724327fc273fa2d61e3705438e60d73
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.