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.
23a20746ee03b297cfcd56e4c1d6c6e842de35556de525fe7d5cbb67ff0c5452
Both payments are on their chains and locked to the same secret hash 20d65a93f77cdaae684f5ec32dc2f0f62960cbb5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 23a20746ee03b297cfcd56e4c1d6c6e842de35556de525fe7d5cbb67ff0c5452
- MakerPaymentSpent: a08f9a43a88f49a9cca4c9c5977fb1db57da7ab38789fb87bdd1d93ea925f0cb
b6d55f5928309ebe56f0ac6377832ed8eefd7f82a867c61d55e183a2b3a1c8a5
Both payments are on their chains and locked to the same secret hash 20d65a93f77cdaae684f5ec32dc2f0f62960cbb5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3ed7cb734dc8e1ad1f44ad4030fcfa1cc1a099b2381b03b4bbee5baf03dc3e50
- TakerPaymentSent · TakerPaymentReceived: b6d55f5928309ebe56f0ac6377832ed8eefd7f82a867c61d55e183a2b3a1c8a5
- TakerPaymentSpent: 4942f7e6e45159ed6dadc1b2b7b13af8033c79e91c812110f2da693fa3c5d458
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.