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.
f7399766730c7dbf25226ebc00156b37444fc96909ec2b732ce05f17a83f98fc
Both payments are on their chains and locked to the same secret hash 27d768accf912fa1604ed2b82c44bbf9aeeb5901, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f7399766730c7dbf25226ebc00156b37444fc96909ec2b732ce05f17a83f98fc
- MakerPaymentSpent: f320cd3362635ebbecb94f6498fefa60f27b245b0b2561830388b26b5b6d5716
6201c41d14598bc42324aa072b7f8fc1ba449ff2ddca1599d9d229664555eb1c
Both payments are on their chains and locked to the same secret hash 27d768accf912fa1604ed2b82c44bbf9aeeb5901, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e9f96205f482345c52ec522a80589c8db34a134c78a1f5d6baf783067b3e9c2b
- TakerPaymentSent · TakerPaymentReceived: 6201c41d14598bc42324aa072b7f8fc1ba449ff2ddca1599d9d229664555eb1c
- TakerPaymentSpent: 45e5108ea7273c9f1c4f81c800ba7f358343990f94e7ff33ab7179b113311531
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.