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.
849ecf6f3171209faa16dce9eb2207114691cc60da3dfc4270194f53f1ffff6b
Both payments are on their chains and locked to the same secret hash 3c9c9848db0587da6fd1680a0c5cf955caa437cb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 849ecf6f3171209faa16dce9eb2207114691cc60da3dfc4270194f53f1ffff6b
- MakerPaymentSpent: 1ac58081f623d26c06ebf09e9a3b4248789a7d5e140b3f47922c0dc6350a8189
5a59899089e732c1a00712f09c476cba34dcf78ff17890f885447b6581101a1e
Both payments are on their chains and locked to the same secret hash 3c9c9848db0587da6fd1680a0c5cf955caa437cb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ee7cdcc5e551a6cab7c2193fd680b4cdbe29b99dde96bea5082354dd58a6e403
- TakerPaymentSent · TakerPaymentReceived: 5a59899089e732c1a00712f09c476cba34dcf78ff17890f885447b6581101a1e
- TakerPaymentSpent: 1b5d604034ca222857fea495b32a7f3075a39ee3dbb5aaddd4dba51274a8c66e
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.