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.
572c9e9f69e6553507d204ea65528005cb338a391e56cbb541c96548cd0ef294
Both payments are on their chains and locked to the same secret hash f990d5fcb04ca8a7517b6da15d894599fa7ccfcd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 572c9e9f69e6553507d204ea65528005cb338a391e56cbb541c96548cd0ef294
- MakerPaymentSpent: c5f4959281b7b085958f5af724efa376ce324da7733be5580b609b6f50205dea
f115b1abc37f0b4254f992061fbe77b6189e070a85e994495cb57f661c6d0947
Both payments are on their chains and locked to the same secret hash f990d5fcb04ca8a7517b6da15d894599fa7ccfcd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0b02c6f2c2c2e869c1b489bc3210f8ba33ac331bf2a2792ab2f8e76eebd676d3
- TakerPaymentSent · TakerPaymentReceived: f115b1abc37f0b4254f992061fbe77b6189e070a85e994495cb57f661c6d0947
- TakerPaymentSpent: 16baba93700d180c2a6ffe6bfabcfe9452cd1b3988c6c3eb5609f69ce6925b99
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.