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.
898e8c0d5757918ab72663bd7881656123586f95433ae977def3a51c60c7361d
Both payments are on their chains and locked to the same secret hash 9e543a8bc136fe60d5c12958046930e00e4b862b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 898e8c0d5757918ab72663bd7881656123586f95433ae977def3a51c60c7361d
- MakerPaymentSpent: ab9ae543d6ba2bc86d4328ead62501479b48b301092ea5570cafe60dd5133fe5
84412109c8171892a48e6bfd9678aba819c2f6428f713e509564a38d79ab775b
Both payments are on their chains and locked to the same secret hash 9e543a8bc136fe60d5c12958046930e00e4b862b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: af9d79c0fdc36e33c242b0308974a5779246401fbdf821a7fe5d01cc626d27cd
- TakerPaymentSent · TakerPaymentReceived: 84412109c8171892a48e6bfd9678aba819c2f6428f713e509564a38d79ab775b
- TakerPaymentSpent: a89a0ee56094cf71ddbfa3dfdd17207028d0f220d892fcbfce480f233b9a1d8e
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.