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.
36e59d7a8cecd5b1f12c7fcc5e41e653367413914dec26993481b819058f93ab
Both payments are on their chains and locked to the same secret hash 7498c521986396f5bfe00152f16110b2f75b7b06, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36e59d7a8cecd5b1f12c7fcc5e41e653367413914dec26993481b819058f93ab
- MakerPaymentSpent: 31f8cacece894d4942214cdb66294071f15c157f1f2349334867ddb9faa3c9e9
43cc18b99cc29851d304f24f4165e6b8703880d329061a841ba8527e2037ecc1
Both payments are on their chains and locked to the same secret hash 7498c521986396f5bfe00152f16110b2f75b7b06, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fb36102b3dd4f0ffda4800c65b88cc7c3126e7ab6b663556cc2093308ea9a5e8
- TakerPaymentSent · TakerPaymentReceived: 43cc18b99cc29851d304f24f4165e6b8703880d329061a841ba8527e2037ecc1
- TakerPaymentSpent: 49cbde8360b9bbfb19b8ccb07921d74920d77c779746ff14c2460e960ff8a00c
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.