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.
ba15fb24e489cd0dab89f10b3e30fbd06c08dd752d410e9265630727e9f12500
Both payments are on their chains and locked to the same secret hash f1e18685556123514322c5940e07238b4e979967, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ba15fb24e489cd0dab89f10b3e30fbd06c08dd752d410e9265630727e9f12500
- MakerPaymentSpent: ae4f8cc2533bf10576d89b0295a723a0922741d63f38a4917a2500374ead51c8
23d8547d7013705d62b15b2849b3a26b7efa6d6091107fa283386c7135dd916a
Both payments are on their chains and locked to the same secret hash f1e18685556123514322c5940e07238b4e979967, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9dc18e06191b4b730fba28159421d971e372fa8e11ad407064088c2a12a229fa
- TakerPaymentSent · TakerPaymentReceived: 23d8547d7013705d62b15b2849b3a26b7efa6d6091107fa283386c7135dd916a
- TakerPaymentSpent: 8609bcafa487027946972943606942288640b2d839af6dd014cd9bcacfa0e583
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.