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.
cd3de86df15b0e82c1deb3e5c7a8c40e92b086a7cc7d639ada51b0a89bf807b0
Both payments are on their chains and locked to the same secret hash e83b57dbe952d3a7d9f8f6bb816971fe988cad2b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cd3de86df15b0e82c1deb3e5c7a8c40e92b086a7cc7d639ada51b0a89bf807b0
- MakerPaymentSpent: 75fefebc5644c7d73e7be99a6fb1ac243c1711389135f103f7acbcd3e0516cc5
b7e83614eb16d9849c3a1b57c4afe4e641f3b617d1c1c13908c849da4682d5d3
Both payments are on their chains and locked to the same secret hash e83b57dbe952d3a7d9f8f6bb816971fe988cad2b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 414499cb90b6f582fa7c3d5a0301562dd7a0437c47c69fe4f27ca0aac590c564
- TakerPaymentSent · TakerPaymentReceived: b7e83614eb16d9849c3a1b57c4afe4e641f3b617d1c1c13908c849da4682d5d3
- TakerPaymentSpent: 4325d5a55da888c8146830d6587459522981177c7e6665e717c57cbefce2c5fc
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.