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.
68cb50f3cb7c1eb29ec305f644a6e640ec1a618c4772f4795ada7d81373450a6
Both payments are on their chains and locked to the same secret hash 69237a916c72a9f1f1d09d8f775740b3e5e19e69, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 68cb50f3cb7c1eb29ec305f644a6e640ec1a618c4772f4795ada7d81373450a6
- MakerPaymentSpent: 58a9a475e27f963801033ebbde4a8263cb5bf7bcd7b94fd73c663bb6d595cc6d
69ec5aa3cabd106d9af166cba03ebab15a57f545627242d4b60a5f5145069e4a
Both payments are on their chains and locked to the same secret hash 69237a916c72a9f1f1d09d8f775740b3e5e19e69, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: feba5a5d24cddbd9c6a6fd0c7d9c8bb25b99c6362532002dc3f0a2cb5517253b
- TakerPaymentSent · TakerPaymentReceived: 69ec5aa3cabd106d9af166cba03ebab15a57f545627242d4b60a5f5145069e4a
- TakerPaymentSpent: 88e69285f2b514178b0b447bfb2d5d20e84b6dba1f8ada9f14cad1b369fe2f52
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.