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.
282f998225adf9ccea74ee3751ce8d80cfdb6fe6c013ea7fe2ada8025a4a89c7
Both payments are on their chains and locked to the same secret hash 741ba784d6465c3c420e906c98c17eebc8b608ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 282f998225adf9ccea74ee3751ce8d80cfdb6fe6c013ea7fe2ada8025a4a89c7
- MakerPaymentSpent: 60c7ea5ed232979868e873ece59207e4336058d3f9561070f13b68a07e72122a
e924981017d10fab65d9841cee711562868db3ee129a835543e87c57cd2c70fc
Both payments are on their chains and locked to the same secret hash 741ba784d6465c3c420e906c98c17eebc8b608ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 844f531bb358a0b66f5c6dd7ce3a35e077f9d9e20d482cf07de71472fb962361
- TakerPaymentSent · TakerPaymentReceived: e924981017d10fab65d9841cee711562868db3ee129a835543e87c57cd2c70fc
- TakerPaymentSpent: 8cf72da6beae92ed47031ef60f2e867a18d95758049f6ff2da2dfa46c865754a
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.