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.
139fd8026738ec09e1fb131cfff16677385c9e93502c1f85589024a0453191b1
Both payments are on their chains and locked to the same secret hash 1ba43c03eb46d76a21f357e054bc636f9179aac9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 139fd8026738ec09e1fb131cfff16677385c9e93502c1f85589024a0453191b1
- MakerPaymentSpent: bd7d83a152461df3cc5d05ea49840f521ffe8de5d3fef803ec6699b36765a6f2
ea35ab0a7fec996af5c724e2790e6b6a195522a014025a2584b83df478a8f042
Both payments are on their chains and locked to the same secret hash 1ba43c03eb46d76a21f357e054bc636f9179aac9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0899df39829842f91989c7993d0a424ba28bb63f865484da380bba70f7d1d968
- TakerPaymentSent · TakerPaymentReceived: ea35ab0a7fec996af5c724e2790e6b6a195522a014025a2584b83df478a8f042
- TakerPaymentSpent: 67aeb0755f88908a562b15b839d6008eb57c44a19395d59e3727e45a7ad4af55
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.