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.
bdf649044a30c263fb832f6a050f49630ee0d0c1e2c765ffea327570e12d9b46
Both payments are on their chains and locked to the same secret hash 6e347edf943908449b3557dcdade9c263db0457d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bdf649044a30c263fb832f6a050f49630ee0d0c1e2c765ffea327570e12d9b46
- MakerPaymentSpent: 0df6e53f64308792ee472ef8e7c13cc4f287a84985e8051c66bf5f298dd7807a
bd381ade1824177ad2fc8b8c506779d034688d1bab003e3131383a56ed594071
Both payments are on their chains and locked to the same secret hash 6e347edf943908449b3557dcdade9c263db0457d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b4f201d0d035185b2aef190f6c4bef70851eaf5aba0fa66746394c756833f74f
- TakerPaymentSent · TakerPaymentReceived: bd381ade1824177ad2fc8b8c506779d034688d1bab003e3131383a56ed594071
- TakerPaymentSpent: 615b03467c36e802364fbb81de36362290b5c2b0401d89b9346e181cb6c55802
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.