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.
ac82d194717923b77b180812b44fdc65b35f7e6ed379ecb7165ff5ed450df330
Both payments are on their chains and locked to the same secret hash 85a778af183933453556c345ea2f32c939714032, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ac82d194717923b77b180812b44fdc65b35f7e6ed379ecb7165ff5ed450df330
- MakerPaymentSpent: 8bcf833ad34f5532714fa862491601efdc36363c88151efc4d1fe06053335e1f
d007154d34c74fc8bd809f36c4a9b6de991e1398dbb1a3c43f3dd03da1c25f93
Both payments are on their chains and locked to the same secret hash 85a778af183933453556c345ea2f32c939714032, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 87138768f2951421807ccb22008dbf5452efbfbd4a32df90c9097ed05cb99722
- TakerPaymentSent · TakerPaymentReceived: d007154d34c74fc8bd809f36c4a9b6de991e1398dbb1a3c43f3dd03da1c25f93
- TakerPaymentSpent: 18839fe6f00c5731fec8733fe04c4fd18b197d9843c9340ca0b737274e30b881
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.