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.
c90fb44d1a1e2bfcdd0b41188c30118e6b48ac39bed9db36e59337ed3db1fc3c
Both payments are on their chains and locked to the same secret hash 442c59df77716097a857ae2395288553d543c37c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c90fb44d1a1e2bfcdd0b41188c30118e6b48ac39bed9db36e59337ed3db1fc3c
- MakerPaymentSpent: b87b735553faadbcf27e2183081e8e9a55a8a4f9e4193efb8bdf8f9cd7fa7d54
5d58e508662fc454aaf5f55813b2a1193204477451f6886282ad91a05adc6575
Both payments are on their chains and locked to the same secret hash 442c59df77716097a857ae2395288553d543c37c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6e007a6f8b4fa5469d7db49271289e038c9022bc1e05187855519ced7b0d117c
- TakerPaymentReceived · TakerPaymentSent: 5d58e508662fc454aaf5f55813b2a1193204477451f6886282ad91a05adc6575
- TakerPaymentSpent: 5ec5ff3ade4833fc03b18d347682919d083e3dcdd50377c449d78012bb65ab75
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.