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.
81349f13c51d530cda7eaebc79e15b7bfd638c2478151a21d3609708fb1c528c
Both payments are on their chains and locked to the same secret hash 61612fad767ac9fcb2e7df6f546d92d2a9f7d805, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 81349f13c51d530cda7eaebc79e15b7bfd638c2478151a21d3609708fb1c528c
- MakerPaymentSpent: 8cf3fccd0a524be0c737090b8972012db23ffb7f9ae13b28c67af00e81404773
74c70a6e748b1d6f77de7f5a9a82b5e4b727c18d0a731612aadcb25e564ab32c
Both payments are on their chains and locked to the same secret hash 61612fad767ac9fcb2e7df6f546d92d2a9f7d805, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 532df3f04e8bfb3ef734bbda62364d2c9597c629f878262d943a331a6b712887
- TakerPaymentSent · TakerPaymentReceived: 74c70a6e748b1d6f77de7f5a9a82b5e4b727c18d0a731612aadcb25e564ab32c
- TakerPaymentSpent: 9eb41e86887a81b4ed660946f75592ef7f03f33425d162f18a93c59fa2cda83b
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.