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.
af9db25f1d0a18f9334eb9189390eba022ad813dc4ce59c6ae3c35e59b5d44ad
Both payments are on their chains and locked to the same secret hash 128f8fefb722bf9d451d89db5b582e069bfb170e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: af9db25f1d0a18f9334eb9189390eba022ad813dc4ce59c6ae3c35e59b5d44ad
- MakerPaymentSpent: d14a1661344c8ea14221b50dc9ede6d803512c8995e2d0af2b96782d4bb59a3f
1444def010b4e3894a684269e2eb5dc87aaedc57a821d6e91648e3acd243b249
Both payments are on their chains and locked to the same secret hash 128f8fefb722bf9d451d89db5b582e069bfb170e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e72ffd1d1e020827b23cdf92085c49eb4500826ec1bf83d2e9e861e4d8915608
- TakerPaymentSent · TakerPaymentReceived: 1444def010b4e3894a684269e2eb5dc87aaedc57a821d6e91648e3acd243b249
- TakerPaymentSpent: 35ed0dd0d6ab7e3a13b208e81ac1805530dd7429e3010d1006804053a4559210
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.