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.
4a6438536311e6b74260d793970fc4d90ef48c5ade153e1ecc4464f44709d893
Both payments are on their chains and locked to the same secret hash f6f9ee1c26c8318d306952bfaa9912a06e0a9373, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4a6438536311e6b74260d793970fc4d90ef48c5ade153e1ecc4464f44709d893
- MakerPaymentSpent: 50bb7ca81b36c6dd1226a3e7423b49748f320126f07decbd125dbe7a53e1eaf9
a8edbaf8c2e823600f71c698fcfebad5d347aff2c4b374e22d949a9ae8680d7a
Both payments are on their chains and locked to the same secret hash f6f9ee1c26c8318d306952bfaa9912a06e0a9373, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dae8657f3dd5808b083320f0991d08b40532ec510177f3598ddfe96797497b9b
- TakerPaymentSent · TakerPaymentReceived: a8edbaf8c2e823600f71c698fcfebad5d347aff2c4b374e22d949a9ae8680d7a
- TakerPaymentSpent: a8d0c25c0ed8a15c093e54753b39718aefad8b4800fbc7016c3ca89411f0190d
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.