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.
0506e0e3a88e519c63463156914cf1ce6bf029eb5ea7d81bf73c87976f1fd120
Both payments are on their chains and locked to the same secret hash f2d3997bc908b4f68cfd7c91df0927f41382877f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0506e0e3a88e519c63463156914cf1ce6bf029eb5ea7d81bf73c87976f1fd120
- MakerPaymentSpent: 84540d64f7481ff01eb55e0e244a300aed58b36b5e3b61a77a7976db7d9bf7fa
39e7fb5ccf15f9b9dbb4d581bdd895725019ffc0a70125316646f9781960b6c4
Both payments are on their chains and locked to the same secret hash f2d3997bc908b4f68cfd7c91df0927f41382877f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f73c82bb7577d3e9fb3c7ef4b1b6e34a4363472c049d1ed19dd4a2e2cce29c0c
- TakerPaymentSent · TakerPaymentReceived: 39e7fb5ccf15f9b9dbb4d581bdd895725019ffc0a70125316646f9781960b6c4
- TakerPaymentSpent: c7e4e637211170b16e7812ab1004892f33a75f13357162a791ceef6f41204931
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.