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.
231886f33f24bd6ad68d62d35661774cee2641008bb58e9c01bdc0e1eff9fbf7
Both payments are on their chains and locked to the same secret hash 8865b82b96b114f72912629b8c578d8387ac6343, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 231886f33f24bd6ad68d62d35661774cee2641008bb58e9c01bdc0e1eff9fbf7
- MakerPaymentSpent: 7fb9103aaac374c826e108475ae6bac0d45461ec2bd9243ba3102e5f87a4cb56
2f4960390af68181aa2cc3301bf2ca9b428be97a7794c39fc286333ea37dc99d
Both payments are on their chains and locked to the same secret hash 8865b82b96b114f72912629b8c578d8387ac6343, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1f58527e9a4bfd7f930474efbabe66fae1e9013cd1323e39116fa6b69a35e841
- TakerPaymentSent · TakerPaymentReceived: 2f4960390af68181aa2cc3301bf2ca9b428be97a7794c39fc286333ea37dc99d
- TakerPaymentSpent: 301a031502b0910ad8c02118715e43754caf7f924a65dfcef8afef64a76e02e5
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.