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.
1c6fbdfc399a6b26c9d726116f07f006182af65145cd1e80654bb94194215e92
Both payments are on their chains and locked to the same secret hash f226f12c9ea869e808a8db179f763ca20e8f1fc2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1c6fbdfc399a6b26c9d726116f07f006182af65145cd1e80654bb94194215e92
9b63e1b06b8eb62c83725e2184b087cab42098679bd6237f0b6c29c6427eaa8c
Both payments are on their chains and locked to the same secret hash f226f12c9ea869e808a8db179f763ca20e8f1fc2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6e3f54c77523452df741ae805bd17160d0e73f262fccc163020f66dd5f3de4a6
- TakerPaymentReceived: 9b63e1b06b8eb62c83725e2184b087cab42098679bd6237f0b6c29c6427eaa8c
- TakerPaymentSpent: 6614fe4d9a43b2826772346ea4045a7125fe0449cc35032853fbc3dee2c49fda
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.