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.
b42ad81a2c73f9a724c5773c98e0a14a2f29475cba0f47c11ab2acade36ee660
Both payments are on their chains and locked to the same secret hash e9f76b19cb7fd2a2b5b760cab3c649be571a5601, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b42ad81a2c73f9a724c5773c98e0a14a2f29475cba0f47c11ab2acade36ee660
- MakerPaymentSpent: dd8d6f7219d548390c0055ab686a54c9ee342f4d0d4693f22f4d247469a44930
4afe5514c36bd5f43d97ba9a77e09ec0e9e01c6298ec12dfb9c93589d4902134
Both payments are on their chains and locked to the same secret hash e9f76b19cb7fd2a2b5b760cab3c649be571a5601, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8c8173b585c144ecbb2ae8244e47a97532b4aafd6b6a16a592ca8ab3dbb8c9aa
- TakerPaymentSent · TakerPaymentReceived: 4afe5514c36bd5f43d97ba9a77e09ec0e9e01c6298ec12dfb9c93589d4902134
- TakerPaymentSpent: 27730407df35ae611e6129591f64005fe07da830779d787fd4707b89d9d99bea
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.