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.
a18c24712e4c5072a7b7d80fe2534c6bb3d22c63468f7bebf79850d185f19d4f
Both payments are on their chains and locked to the same secret hash f3ba58685df987645523c0d98ff4151db1ec0506, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a18c24712e4c5072a7b7d80fe2534c6bb3d22c63468f7bebf79850d185f19d4f
- MakerPaymentSpent: d53e1ce2753b839e275afb105f8b57cc323e7087ec0e6e1d3026f04fc73406a3
8a3571630d521aae6fdaa191ffe2e5407bea6834c92f16e044802891feca139b
Both payments are on their chains and locked to the same secret hash f3ba58685df987645523c0d98ff4151db1ec0506, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1feb755d77097b41ca83214e5491aab701641f8f20599ee1539b2b520213cd15
- TakerPaymentSent · TakerPaymentReceived: 8a3571630d521aae6fdaa191ffe2e5407bea6834c92f16e044802891feca139b
- TakerPaymentSpent: 2e4e66a842e155ffa059555f265e058d6163ed145d90c6a1218da444b90213ce
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.