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.
4b6ed2ece5f01139774890e77e5eb89bfcfa67208049951184461d4fb19ce54b
Both payments are on their chains and locked to the same secret hash 90d1a8b9cb8dbf650203eed21c794bcd1e0a928f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4b6ed2ece5f01139774890e77e5eb89bfcfa67208049951184461d4fb19ce54b
- MakerPaymentSpent: 3160c9d93accf35eeeb500470cfe183b575289354754f93ca5a183154beff18b
b0f9b4eb7efb483011ad4766d55ec43c26cb0f41e514cd19485db1e7cd128a3c
Both payments are on their chains and locked to the same secret hash 90d1a8b9cb8dbf650203eed21c794bcd1e0a928f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b6435a28b8f76a58d3ecee2dff1b9ec775854d724dfaa6b1ed15e1d76bb80d6d
- TakerPaymentSent · TakerPaymentReceived: b0f9b4eb7efb483011ad4766d55ec43c26cb0f41e514cd19485db1e7cd128a3c
- TakerPaymentSpent: 6d4f2d31f03b38ec97cfde89a66a773ec52ac63a08792647da1196b460e10133
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.