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.
74d483e398bf82ff9c79e75692141aee31b62ec0b33420e0fb51cfcdbb1577fe
Both payments are on their chains and locked to the same secret hash 9f390d5e019b518237d37f2a140903ad287f4bfe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 74d483e398bf82ff9c79e75692141aee31b62ec0b33420e0fb51cfcdbb1577fe
- MakerPaymentSpent: 149b0746d95adff1e67bb2120a78cce525fc361533f3a6aedab76fd268edfd9f
67db4a9ad1212bf51697cbbe21f74b2be2f295d609a88a429d7204765597c259
Both payments are on their chains and locked to the same secret hash 9f390d5e019b518237d37f2a140903ad287f4bfe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 55bf37f530b7e8c2cba5e2bb09d9b8d9bef65a647a6a7c30132720ecefe6e737
- TakerPaymentSent · TakerPaymentReceived: 67db4a9ad1212bf51697cbbe21f74b2be2f295d609a88a429d7204765597c259
- TakerPaymentSpent: 45d4c920095d1058ec64d66994b1d6745dc49c846a76f62f6cae1124d0711299
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.