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.
4e96a5e0c3dfbb61589fad14c76e6d27bfb186aeb13da3ea9f516859e5a66349
Both payments are on their chains and locked to the same secret hash f4c54cfd28ee6b629aee2a4cfa7349787e4afc58, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 4e96a5e0c3dfbb61589fad14c76e6d27bfb186aeb13da3ea9f516859e5a66349
- MakerPaymentSpent: 0273de5d291af22f80a177d45df92ea5ef39eb04a63671aa35fb97fe5afc3d93
8f267ea3616aa34bf6c5cb8e384d41f81ffcdeb0d71667208a618a3c5bac1322
Both payments are on their chains and locked to the same secret hash f4c54cfd28ee6b629aee2a4cfa7349787e4afc58, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 27c04e6c9feb238b5f389c3b31d5b5ff8d9005ce5c2539a5f491cd9a6b9340a0
- TakerPaymentSent · TakerPaymentReceived: 8f267ea3616aa34bf6c5cb8e384d41f81ffcdeb0d71667208a618a3c5bac1322
- TakerPaymentSpent: 71d13f2a9f7c3aeb8653b9ade6f686b807bedfe9cc56552989186e68b3bc15a7
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.