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.
d4cb1ee8d1073c048e7fbd0f1793c26172721d6fd830e7b4b87568d7d7112710
Both payments are on their chains and locked to the same secret hash 46aab833cce8fd2a56320778abcb92fa937cc066, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d4cb1ee8d1073c048e7fbd0f1793c26172721d6fd830e7b4b87568d7d7112710
- MakerPaymentSpent: b4ad6ac6276df184923c691364c87e05aee38bc77662d9a30376f02a949a184f
da80691372ceb55e959eeff14996d34fbbf1e49155399521a1ac7251b707a962
Both payments are on their chains and locked to the same secret hash 46aab833cce8fd2a56320778abcb92fa937cc066, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4f87b6b86618eabd252084c512eca6c13b0fecef90c7e63ac4ee2424fcb26190
- TakerPaymentSent · TakerPaymentReceived: da80691372ceb55e959eeff14996d34fbbf1e49155399521a1ac7251b707a962
- TakerPaymentSpent: a54513fbeb6db701f070c3a95740db354a74424caa33e078bab31deb54a12702
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.