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.
f5976a555732f542edac55696f3dec140a900f857c6d8ac8d752986ed4b38158
Both payments are on their chains and locked to the same secret hash f0ebe6c84c22020d393f97defe37c868a4c5ce41, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f5976a555732f542edac55696f3dec140a900f857c6d8ac8d752986ed4b38158
- MakerPaymentSpent: a874d21efc6276c6dafde09f011dcd121994d7c19fa225ba08a57630971c7999
c475a1ab43f79fcf01b86f9d6c4726c75e3d641fce80be1b764195f92a7efed7
Both payments are on their chains and locked to the same secret hash f0ebe6c84c22020d393f97defe37c868a4c5ce41, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 88adce3f74e8868b0e1abd6da551fca9ab63183d4a52cb7712cd607f5201165d
- TakerPaymentSent · TakerPaymentReceived: c475a1ab43f79fcf01b86f9d6c4726c75e3d641fce80be1b764195f92a7efed7
- TakerPaymentSpent: c0edda8334491114e08c5184116b48166c2a2c258176b59c64fc7858cedbbd50
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.