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.
68fdb269ed71f6e5d0c51094c192d72fd3a046066dd2076787e0f5d24dcd2bf6
Both payments are on their chains and locked to the same secret hash 60714d94e03655d9961dc43cec0ed6f9d6ba41fd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 68fdb269ed71f6e5d0c51094c192d72fd3a046066dd2076787e0f5d24dcd2bf6
- MakerPaymentSpent: 2a7b66ea312f00359d6179d609806fa038f6055e3d7d39a604d44ec47d361917
b5a8692020b4ad8aa1135d8118fb130401a3267409a300fdeb5b79748158ec44
Both payments are on their chains and locked to the same secret hash 60714d94e03655d9961dc43cec0ed6f9d6ba41fd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 399a9d2d8413a3461da64ed7bb011fbbdc638dd74f17a3962b11c0c12a610ecd
- TakerPaymentSent · TakerPaymentReceived: b5a8692020b4ad8aa1135d8118fb130401a3267409a300fdeb5b79748158ec44
- TakerPaymentSpent: cfcb6f8288fcbef8c87765a2024b8d4278d9689c009ea0fbe060a9cf68a48ca5
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.