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.
54bafc0a454b72b12e6192e8cf4a7216aa6f2a63a96212fd559059e1a2bd7685
Both payments are on their chains and locked to the same secret hash fc46f1794bc1a6e41515ba51322f789093a6e113, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 54bafc0a454b72b12e6192e8cf4a7216aa6f2a63a96212fd559059e1a2bd7685
- MakerPaymentSpent: 2c64a4b88f299e657101d292886ffdaaaa8cb9e0c49a16fc20149e5adc46db0f
57c36e667ef1d011aaa7f03916a5360e90fff2a9b58abb0f60fb6e4f87617bd9
Both payments are on their chains and locked to the same secret hash fc46f1794bc1a6e41515ba51322f789093a6e113, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b04543ea57c0872ea3b11c1dde131dc8de8935841371274d08c1ffb66a3ee3f2
- TakerPaymentSent · TakerPaymentReceived: 57c36e667ef1d011aaa7f03916a5360e90fff2a9b58abb0f60fb6e4f87617bd9
- TakerPaymentSpent: 56e66dadece7a59514bd6dd5c7e3bc045a42e22308ac6be4ac53f19cdc5647ce
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.