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.
5e9805210fcfb47c4ad505e93718cccd338ae48273d812510682f00b56f9c4d9
Both payments are on their chains and locked to the same secret hash 0f0352d325f4be7abff12938912df46c582bd4eb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5e9805210fcfb47c4ad505e93718cccd338ae48273d812510682f00b56f9c4d9
- MakerPaymentSpent: 3caf4f98d353e9ca3dd5a403d7ba0585412d5e156487dc3e44e44e9cdde6a782
bc9069728c1ff4208e9f8c1f1606fd55de84e2f6b71d20b097dd50f6c5188f51
Both payments are on their chains and locked to the same secret hash 0f0352d325f4be7abff12938912df46c582bd4eb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ad61095448223d41d388220b95b5fba120a401bb9f038b382a289a53e62ce6e2
- TakerPaymentSent · TakerPaymentReceived: bc9069728c1ff4208e9f8c1f1606fd55de84e2f6b71d20b097dd50f6c5188f51
- TakerPaymentSpent: eb6630b22d8ade9fcd9dabc11a1e2dd53df60384ed3f2f1c4b1a6f87f1bfe35b
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.