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.
441e47e8743fcdea8bc5604ae249b4a1fb8af5ca5a752c5858dd2189fcdb95de
Both payments are on their chains and locked to the same secret hash 10d61c72daa255a2d15bf706446d742eca3e5069, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 441e47e8743fcdea8bc5604ae249b4a1fb8af5ca5a752c5858dd2189fcdb95de
- MakerPaymentSpentByWatcher: 3c7b0747c788ca849bfed96c1d057ad4bfe3fe43536a0aa464f966040af980c7
4873c6d80d0fb37167181f2cc9e8d4035ca77bcd6e85e8b1dbf3df5b52f41e90
Both payments are on their chains and locked to the same secret hash 10d61c72daa255a2d15bf706446d742eca3e5069, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 95474cf0be00a63672c46554d42cadd9d9cb0ea519687a725a019d87cb25b1df
- TakerPaymentSent · TakerPaymentReceived: 4873c6d80d0fb37167181f2cc9e8d4035ca77bcd6e85e8b1dbf3df5b52f41e90
- TakerPaymentSpent: 7bc7b8eab1a241140c94d186b7c1c6108b228484f599dda7b757a13521556015
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.