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.
d7b23f3e5dacb66e53b2f6b985b625d01dbcdfb6450b1002de321b9f7ca8efee
Both payments are on their chains and locked to the same secret hash 51c331712fb093c6b99775c2a6f8ce1ade3f9ace, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d7b23f3e5dacb66e53b2f6b985b625d01dbcdfb6450b1002de321b9f7ca8efee
- MakerPaymentSpent: 9e2c35fea715e72a58d9d43dfd9c9ad30ae1c5fa8cfcf86a865b8033f251d367
751ff3a58622b8236b4759c76166bc219841790e050683a985fdc94d602c8248
Both payments are on their chains and locked to the same secret hash 51c331712fb093c6b99775c2a6f8ce1ade3f9ace, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2e1d010f9793aeb2e918362c9e896b7281569a6110f9772e9e1eda6dad675233
- TakerPaymentSent · TakerPaymentReceived: 751ff3a58622b8236b4759c76166bc219841790e050683a985fdc94d602c8248
- TakerPaymentSpent: 7b07319a3617d59664e27d44c5d5fb4b7f62b6eabb7e0717c5385c9fac144a04
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.