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.
99d36303646cdbc16981813254a7d38c14b1385e6adee52555ee010e22b74d85
Both payments are on their chains and locked to the same secret hash 8a25bd128d9aab1fbdf448f8702eee5fd2362b98, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 99d36303646cdbc16981813254a7d38c14b1385e6adee52555ee010e22b74d85
- MakerPaymentSpent: c2f9503041c1fc4b0f2b11b05ec1980d693e2211a668c9446ea6b4c71f868d5b
0f250af3a3a6c69c820396fc51064b80d2226983e42880ac4f1240e9c6be99ef
Both payments are on their chains and locked to the same secret hash 8a25bd128d9aab1fbdf448f8702eee5fd2362b98, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3e15d93d1da215092df9032ce9800d15bf864736a52b560b95f643e5c465cc84
- TakerPaymentSent · TakerPaymentReceived: 0f250af3a3a6c69c820396fc51064b80d2226983e42880ac4f1240e9c6be99ef
- TakerPaymentSpent: db076b4857971daf4781ac54e928a63ea10e96f564151fa6091d821fb9fe9417
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.