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.
89af0072947ddff8dec1f00c50d17708f41ab3b63a4b8c938c20badbaf188135
Both payments are on their chains and locked to the same secret hash 9bf386a388fa20a7f897fee10d906bc2d3d6014a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 89af0072947ddff8dec1f00c50d17708f41ab3b63a4b8c938c20badbaf188135
- MakerPaymentSpent: 15200dc66864d9a2b8d69d0e0834ed118737ae8455383d646b6b13921d8c0be7
78d34f4ccdc8fd8127842a536295c042ade53b2990eccacb36cc36c51947df43
Both payments are on their chains and locked to the same secret hash 9bf386a388fa20a7f897fee10d906bc2d3d6014a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aeba6a01525ff9b2165132fe6e206fba0af1d0c4b34825b1ad61e00da19ae793
- TakerPaymentSent · TakerPaymentReceived: 78d34f4ccdc8fd8127842a536295c042ade53b2990eccacb36cc36c51947df43
- TakerPaymentSpent: 8148b724b6109fa2a99cca45012f80bc684cfd46f41203d1b30ea779ebf2b7ac
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.