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.
cd61cb84cb691cd95c99bcb4652b1ade0a461d4842de40e40b84b6d33cb2926d
Both payments are on their chains and locked to the same secret hash ad73d9440974d9d52a890739ee6632f240106841, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cd61cb84cb691cd95c99bcb4652b1ade0a461d4842de40e40b84b6d33cb2926d
- MakerPaymentSpent: 20489fb6a38af7375f65705733e94ee55d62e56dedf96aebe1ed33482704b75c
6e1299699f050acc4590d6b92d2e110c5cfd8087bf96319a6780b4423f5ccbd4
Both payments are on their chains and locked to the same secret hash ad73d9440974d9d52a890739ee6632f240106841, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cb232345f4e8f03dfadb03da2388eed918fc7fa3256b668e55ddb42d5f172209
- TakerPaymentSent · TakerPaymentReceived: 6e1299699f050acc4590d6b92d2e110c5cfd8087bf96319a6780b4423f5ccbd4
- TakerPaymentSpent: 49cc9de93f62ec988edc3cbebe0d56fc70311ae6494e4721f665e33ca627a729
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.