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.
703d9f077a5aaef1ae4b5a32b19632b7878013273a4d1c5fbccfccd83734886f
Both payments are on their chains and locked to the same secret hash b25c13c41792adf4d7bfbabb5798292d673b6846, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 703d9f077a5aaef1ae4b5a32b19632b7878013273a4d1c5fbccfccd83734886f
- MakerPaymentSpent: e422a1f6ada314319e8eb1cc1ddd49502400f1cd21d67bc5263156f3394457b4
215baa57388f1fff491c95a0e5686e4cce8016bc46478a3fa2e5020cec811347
Both payments are on their chains and locked to the same secret hash b25c13c41792adf4d7bfbabb5798292d673b6846, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e352f69e73b9d36b8e9508e77a3defe3f8fb134c7c99612c84747e36300c20a1
- TakerPaymentSent · TakerPaymentReceived: 215baa57388f1fff491c95a0e5686e4cce8016bc46478a3fa2e5020cec811347
- TakerPaymentSpent: 0639948e83719cbacd5933a4300eec79c5736154c8d2a948eacffe9f55bfc619
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.