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.
4e80e5255520bd0b2d53da2b233abd580b61c54b05e9bfb11dd98a7762b4e2ce
Both payments are on their chains and locked to the same secret hash 0623f92f1e0a4d0e242ff7d30056067c747114b3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4e80e5255520bd0b2d53da2b233abd580b61c54b05e9bfb11dd98a7762b4e2ce
- MakerPaymentSpent: ba8cdc0244d7191bd8c68f14dfb7527dd4fd043958805521058ae47a9aaeebdd
01cced0ef98002682a491554d525dff4d91b0608da395e981498352e66c73f41
Both payments are on their chains and locked to the same secret hash 0623f92f1e0a4d0e242ff7d30056067c747114b3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e8692e1e6d8fb4f437998ec19e91ba7db24d2bc4c66fae0091d4acf0543178e7
- TakerPaymentSent · TakerPaymentReceived: 01cced0ef98002682a491554d525dff4d91b0608da395e981498352e66c73f41
- TakerPaymentSpent: a40fc695009ddf30ea178444af09f86546c430090e3f348b2d40877ea4be12f7
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.