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.
67f59091cd31d45d85e314dfa8a802f923dfa7e95073e9f1c5676353173ba28a
Both payments are on their chains and locked to the same secret hash 183831982889aaf62de916b37248790654a784d7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 67f59091cd31d45d85e314dfa8a802f923dfa7e95073e9f1c5676353173ba28a
- MakerPaymentSpent: d5932bde02738e4091b0a3f91e3a85d79d46ca761e756fdf0caa59748103529f
23cc14cb981cf695e635249144e7de4db31f73847a1164b6552572795f73a1c9
Both payments are on their chains and locked to the same secret hash 183831982889aaf62de916b37248790654a784d7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9c7bd18c9ac7ddb8a10b61cae944f7bb7d0955bb8b20dd9f2e74f659c967cf52
- TakerPaymentSent · TakerPaymentReceived: 23cc14cb981cf695e635249144e7de4db31f73847a1164b6552572795f73a1c9
- TakerPaymentSpent: eea1a9489c87a287c7f8c7581c2a253180ba219ee55a736ee25a50443f167401
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.