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.
927a797461de051d05713e9b65c410d8340ea721bc0c6f813077a9f37081cff1
Both payments are on their chains and locked to the same secret hash 8f50282761edbb84a18c04ca1a060942edc3b489, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 927a797461de051d05713e9b65c410d8340ea721bc0c6f813077a9f37081cff1
- MakerPaymentSpent: 8bce76c201aaa1ef7189855cfc8d27a4a47546e9d6036211a06c0bd2b6c89976
78c0f6f2ea4f4ba147c4b418603958e910683360e28f21429865e086f3ff7a0f
Both payments are on their chains and locked to the same secret hash 8f50282761edbb84a18c04ca1a060942edc3b489, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7997cc0d5fd1f00c7029fc4df53dd63d6911ee90398b2bab5f4ae968eac415da
- TakerPaymentReceived · TakerPaymentSent: 78c0f6f2ea4f4ba147c4b418603958e910683360e28f21429865e086f3ff7a0f
- TakerPaymentSpent: f4aaa741b671779d1a04c4198f34d976188187ac73b7db3f4e671ccbc4ac926f
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.