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.
1fac2500b97c66960848e76be8813509b8840a3b1f562127932052d63bb9c6f6
Both payments are on their chains and locked to the same secret hash 17b98aa7df50907d1a91f6bb17394f87ae90f359, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1fac2500b97c66960848e76be8813509b8840a3b1f562127932052d63bb9c6f6
- MakerPaymentSpent: c2cb6d63fa430544e2ec9cb5c703a0406b3805954a4f6fb0d9ca035b94162776
dc360cfed9bfbf30f79ac148e59a63814429af5efadd94637336922ea6643214
Both payments are on their chains and locked to the same secret hash 17b98aa7df50907d1a91f6bb17394f87ae90f359, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e999e972695818e75f381198a592bf15c8224ceadca53194762462d160c8d2aa
- TakerPaymentSent · TakerPaymentReceived: dc360cfed9bfbf30f79ac148e59a63814429af5efadd94637336922ea6643214
- TakerPaymentSpent: 44dc019aebd3f847bc0609f00faad65608f052aebcdee42199c6a744c56a3e4b
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.