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.
ffa9974f88b7af89a7832b8bdd6ef2250fea9e87e7d614e94ca1a436e26a5f39
Both payments are on their chains and locked to the same secret hash 7313403b1a68a3b2640032273fa5d2bb4c5d7eb0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ffa9974f88b7af89a7832b8bdd6ef2250fea9e87e7d614e94ca1a436e26a5f39
- MakerPaymentSpent: 84294d1fb059a2a246d9ac5fd9ba4af0888c44b66edde53ace8add83c392646d
38ea0a9f85c8b3063c7c121785bfe43840ce3e9796e0c4ad70fc619d62b71681
Both payments are on their chains and locked to the same secret hash 7313403b1a68a3b2640032273fa5d2bb4c5d7eb0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 09c33c332a65f36c46d69009b28e83199efb50b22b56d538c5cc77322cbc7375
- TakerPaymentSent · TakerPaymentReceived: 38ea0a9f85c8b3063c7c121785bfe43840ce3e9796e0c4ad70fc619d62b71681
- TakerPaymentSpent: e14586a0a05f0106b837a4ad3de7675d531402c7a7aa7da45e4e0d44fb89113c
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.