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.
83aeb86a1e8d5311e6d3aacc93f96dd82acd3d063dba2860b360b03034471c14
Both payments are on their chains and locked to the same secret hash 687565fbf6b9886cf0c81ae91f27a186cd60a11e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 83aeb86a1e8d5311e6d3aacc93f96dd82acd3d063dba2860b360b03034471c14
- MakerPaymentSpent: a06af1282093404d19c74ff5d60788986b3dc1e00118a473918cf40e03e5d1f8
6d3d10bf88cf2a91a3e9aa283a6ac5d3f8278fa49a8b2dc0271b0ede3f3b760f
Both payments are on their chains and locked to the same secret hash 687565fbf6b9886cf0c81ae91f27a186cd60a11e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0db5a191fadb84f79917be49b3a69f84217ad54ce737cde0fa391a19d1f4c2de
- TakerPaymentSent · TakerPaymentReceived: 6d3d10bf88cf2a91a3e9aa283a6ac5d3f8278fa49a8b2dc0271b0ede3f3b760f
- TakerPaymentSpent: 9d5ff43105983cc15f55a4488510c7e35c3aec57346f5147f1d8a5846a57bf95
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.