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.
e007c936248bb176f50b0e4560ca945ec606ae9a8b0c2dfa24d90a8a7604c792
Both payments are on their chains and locked to the same secret hash f968bcfe96802f0bc5efcf5c30aae5ee5b31ce4c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e007c936248bb176f50b0e4560ca945ec606ae9a8b0c2dfa24d90a8a7604c792
- MakerPaymentSpent: 5a21843ff006e5c0444f201651ce143c4965db09197c28e3dcef56d81495b044
40ec6690902f3f1f425a1d874efebc2cf88395b4650a273d48ff9aa3ea5792b3
Both payments are on their chains and locked to the same secret hash f968bcfe96802f0bc5efcf5c30aae5ee5b31ce4c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5d8249c42e8ecd6dd967c68dfa2b1c74340cc9f73c6745b2e7a16893cec60152
- TakerPaymentSent · TakerPaymentReceived: 40ec6690902f3f1f425a1d874efebc2cf88395b4650a273d48ff9aa3ea5792b3
- TakerPaymentSpent: ac00b6c5f875b24792eadfddfa871388b9823c3ec77055ed45c6453558e80b86
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.