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.
0e5f028b6b9b6f2772aa80fe30832b440a8f33c15abf3d546cb1125d19b5c7f2
Both payments are on their chains and locked to the same secret hash 2e2b97f038d9287c906881e83d9300803b8c697c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0e5f028b6b9b6f2772aa80fe30832b440a8f33c15abf3d546cb1125d19b5c7f2
- MakerPaymentSpent: 751e73dc9a01093ef438c27e444edfc029e01269f7f2c3440d8074ff59c1fb76
a8796b79368fccf1b30390cce62adb1dca7bca7854e22f323f67db4f00dbf4c4
Both payments are on their chains and locked to the same secret hash 2e2b97f038d9287c906881e83d9300803b8c697c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 44c29c9c193a5ce5f91b7b33d689742d5b11ebdd21a2ba7f3ad7a38052c774b5
- TakerPaymentSent · TakerPaymentReceived: a8796b79368fccf1b30390cce62adb1dca7bca7854e22f323f67db4f00dbf4c4
- TakerPaymentSpent: 075551f67544869c62f6a9617bede38a01bc0b084a7c98b30e132d7b53b97d74
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.