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.
2bb173c4bae4d66bcee3587157f5f0631cf739d2ea35e9fd5259a02e28f7a8f5
Both payments are on their chains and locked to the same secret hash ac3c5b3210f2c6f86dbd14c31c4233b109e688e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2bb173c4bae4d66bcee3587157f5f0631cf739d2ea35e9fd5259a02e28f7a8f5
- MakerPaymentSpent: 53e16f69d2d4bc93c51aa4885223fd71b64a88e6a5f938d2a083ba68f0df6bac
52c9ae2ce41f6b2628553bceb044dc8ada08a99e055c16e729edfa4439cd23b7
Both payments are on their chains and locked to the same secret hash ac3c5b3210f2c6f86dbd14c31c4233b109e688e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e4dbff586e3901dbf8d29f167a7630de0a80dbca9a457cb3e5911fbca4d04e6f
- TakerPaymentSent · TakerPaymentReceived: 52c9ae2ce41f6b2628553bceb044dc8ada08a99e055c16e729edfa4439cd23b7
- TakerPaymentSpent: 7ecece0e84ffbad47b7bfec422299acb8cef43436de7f044fb44ea9789eec7c0
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.