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.
6e3282536234ee3fcbaec061f65b78e8571b3e3a39c2b2429ad8c88086fb2bef
Both payments are on their chains and locked to the same secret hash dde2d8a43dcf233007ea1c27171bf17f14df09aa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6e3282536234ee3fcbaec061f65b78e8571b3e3a39c2b2429ad8c88086fb2bef
- MakerPaymentSpent: 049f83c9766d59dea9bfc2264cf0237f0a7af84c601734ea70367cf0c6db35fd
c6b0e1e93dce8dd800a005883c9e3c93949dc3f4ae6ee30bd524fd1f43f954fa
Both payments are on their chains and locked to the same secret hash dde2d8a43dcf233007ea1c27171bf17f14df09aa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0ce28de4198434b328aec37815717a9fab0bf7951c009bec1c79e7c2daf0ae95
- TakerPaymentSent · TakerPaymentReceived: c6b0e1e93dce8dd800a005883c9e3c93949dc3f4ae6ee30bd524fd1f43f954fa
- TakerPaymentSpent: b40aa3ffa41de720f766e13d83238de8af2cb92ff5a331d287e4816218ac033f
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.