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.
65dee2115cb014ab50abf906e6dfb3e65d2ee074c91507ed463988303578a511
Both payments are on their chains and locked to the same secret hash 2b923fc7022d35db07b3e228d8e5e0ba1cd5deac, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 65dee2115cb014ab50abf906e6dfb3e65d2ee074c91507ed463988303578a511
- MakerPaymentSpent: be27fcf7f37bd74ebcf9a57406e67614677ca4635032be5f23dee19201ef68f4
d5561293a4cf750e3b0b8c0775b1fc040235d3e0f453c025479899fa6490be95
Both payments are on their chains and locked to the same secret hash 2b923fc7022d35db07b3e228d8e5e0ba1cd5deac, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3965f04b2757a42cfa358aa9725320df8484beebb6cf327e8d54fbf6f49f2582
- TakerPaymentSent · TakerPaymentReceived: d5561293a4cf750e3b0b8c0775b1fc040235d3e0f453c025479899fa6490be95
- TakerPaymentSpent: 69093254d2f1e0a50b29c86333a01a35b4eac09fdf3f6976ce94396937764e01
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.