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.
b384681818e7da90b772c1e67eb6a1796df23213ca1e40ff5145e3733597c7f8
Both payments are on their chains and locked to the same secret hash 98fc03fc9a619a4180a3782d6e44ae91ab0233ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b384681818e7da90b772c1e67eb6a1796df23213ca1e40ff5145e3733597c7f8
- MakerPaymentSpent: 7b3313506e45a0a24759b17ca72ac142ea1f5be57e067dc823864e7cf399b919
dbfdd8995cc4b604ac5593d7e8c3a22637ff614656bc19cf5ae8201947d67197
Both payments are on their chains and locked to the same secret hash 98fc03fc9a619a4180a3782d6e44ae91ab0233ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1922153dcb03dbca54ecb582f76c933d6d394b8ad42b1dc75712027167ca0995
- TakerPaymentSent · TakerPaymentReceived: dbfdd8995cc4b604ac5593d7e8c3a22637ff614656bc19cf5ae8201947d67197
- TakerPaymentSpent: fb179594855ad0c2c8ab9a30cd0d8c9c944ce2c1f6185096031407b4a52283ae
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.