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.
619481480df907b6e22ba9996b45757e1d8d0b4a1e44a6edae0c961a8e54fbb7
Both payments are on their chains and locked to the same secret hash ac88ce9f9b28d6441783489ee3a0a7484783bc2f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 619481480df907b6e22ba9996b45757e1d8d0b4a1e44a6edae0c961a8e54fbb7
- MakerPaymentSpent: e661a4b09eb30e1b9bfedebb3c108c778c34c2c10ee733d352fbab1c22b53525
484e637273c072a8d04c6ef71cbd22f1f4668fabe8ab556da7af3c24d63b9b5d
Both payments are on their chains and locked to the same secret hash ac88ce9f9b28d6441783489ee3a0a7484783bc2f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8ee876a760309bcf5da6e6908d5c4006a0c8c6a29c50d5c1fe9a29cc4c41a0f9
- TakerPaymentSent · TakerPaymentReceived: 484e637273c072a8d04c6ef71cbd22f1f4668fabe8ab556da7af3c24d63b9b5d
- TakerPaymentSpent: 155a2f9793358393cc00d6b64b2ad3406072f0ebfca7744931cb032ce6a7ed62
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.