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.
2af318c36bf5d4b71eefac4516444edcaed6bed69437e17dc212ca9fcc9e9682
Both payments are on their chains and locked to the same secret hash 5c9e67495c351cbb2cffe6fc51ec8332b0402c61, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 2af318c36bf5d4b71eefac4516444edcaed6bed69437e17dc212ca9fcc9e9682
- MakerPaymentSpent: 573d6650103c8587b5c7766e51e4bd18a8a828b60e6ac8e6e5687b242f3e1e36
9fca2fc2aefaac428edba7eb140afcf7366bba5d2fc5490176513a7ec7b58786
Both payments are on their chains and locked to the same secret hash 5c9e67495c351cbb2cffe6fc51ec8332b0402c61, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c11a493a24f8c3880927fe9a30dcde2bb2e6f57ca88a520358fd3dca3ce2ceac
- TakerPaymentSent · TakerPaymentReceived: 9fca2fc2aefaac428edba7eb140afcf7366bba5d2fc5490176513a7ec7b58786
- TakerPaymentSpent: a8349c26c14db90a774d8eef8c27b922498133c265dcd367a6370b6053cfd23a
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.