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.
7059de60cbbc2fda53a0a04a37cc9a88de240208147c8e915b0d499af9949591
Both payments are on their chains and locked to the same secret hash e1b760d5cc61c3491cfbe6b0969085ee1cf0683b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 7059de60cbbc2fda53a0a04a37cc9a88de240208147c8e915b0d499af9949591
819582c3a623934b7906ed67d90b9c43c5a7c2832b34b0b88df898800b6d8e2f
Both payments are on their chains and locked to the same secret hash e1b760d5cc61c3491cfbe6b0969085ee1cf0683b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 9395afe4ef1fccd36cc55ccedbd81da80e1238c4edc671359d24bb3bf19f4b10
- TakerPaymentReceived: 819582c3a623934b7906ed67d90b9c43c5a7c2832b34b0b88df898800b6d8e2f
- TakerPaymentSpent: f6c8606987f3bf5a45489afbf3216ed11a79dc617568f014268793635599f924
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.