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.
92edaae787b2f7859ec71e8a93b603a56eb2846308ba1e2ce04d01021fb27274
Both payments are on their chains and locked to the same secret hash f761fdfb50792fe7c61cd633606f85ed3c1c2289, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 92edaae787b2f7859ec71e8a93b603a56eb2846308ba1e2ce04d01021fb27274
- MakerPaymentSpent: 98580916a644e8d8da70502f475971779fe9afff7981dbd8b304c79e84d44cc6
b2b7a827833e2663d105289444ebbc532dbe889e600b9a122840b968779e4e4c
Both payments are on their chains and locked to the same secret hash f761fdfb50792fe7c61cd633606f85ed3c1c2289, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d5866701036231fbf3437446a245303297db3e0dd1b042451cc3d8c444419409
- TakerPaymentSent · TakerPaymentReceived: b2b7a827833e2663d105289444ebbc532dbe889e600b9a122840b968779e4e4c
- TakerPaymentSpent: ae89e91fbccf2dcfc1d734a46c0a1f89824e3967103813d53add637d250d8cad
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.