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.
80f727c96bbee13356714abed6acabfd9d776b531e2759ca2d931d020d3d11c7
Both payments are on their chains and locked to the same secret hash abd0e4181830ee4dce9498b4d6f1ef33406c420f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 80f727c96bbee13356714abed6acabfd9d776b531e2759ca2d931d020d3d11c7
- MakerPaymentSpent: 4cea08328239014877bd988fdcb9f24575c21c498ea45004315306e647a08b94
128f802d981fade1f89255d6cca285fa2e9c85e577f2c450d36c4d8c7c28777c
Both payments are on their chains and locked to the same secret hash abd0e4181830ee4dce9498b4d6f1ef33406c420f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 72910ee6d2746ce440bfc2d69ff8274d4392901cefa0a06b47116e67440f058a
- TakerPaymentSent · TakerPaymentReceived: 128f802d981fade1f89255d6cca285fa2e9c85e577f2c450d36c4d8c7c28777c
- TakerPaymentSpent: f546730ee391cefaeda2bd743001d2afca6cabbda870d41791effc8d31367dbe
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.