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.
4d7524ceb0f531f5b5925a99ca5cad38eaf52e56cee10c31fceafe7de91d7886
Both payments are on their chains and locked to the same secret hash 63dee522f52672cf11fed03c7a8ba6e54f41c0ab, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4d7524ceb0f531f5b5925a99ca5cad38eaf52e56cee10c31fceafe7de91d7886
- MakerPaymentSpent: b17f74e27b6f65d2480a9e7308aef84e4b374cb4deb0791d49d7a8c5193ab179
2fd2d59317b2c66ef6bc73c4c354df67a1ce68f4099a73eac5522ccb6c19f3c5
Both payments are on their chains and locked to the same secret hash 63dee522f52672cf11fed03c7a8ba6e54f41c0ab, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 77fc1f96c3bd1fb1bf340ea27be47143ca7eba56a45859256b9a083395487c7e
- TakerPaymentSent · TakerPaymentReceived: 2fd2d59317b2c66ef6bc73c4c354df67a1ce68f4099a73eac5522ccb6c19f3c5
- TakerPaymentSpent: 06665adbe4503e4d05937d49718a0380fa63b6dad00cea5e11db14d08d29262d
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.