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.
9c2e8b69a3ae9cbc7dc067b90294f6be8eb9310e278c4e121b8a9edc1d8bdac5
Both payments are on their chains and locked to the same secret hash c0b4de8c0f348e4bfb26cfdb8f03c07c8fa13e55, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 9c2e8b69a3ae9cbc7dc067b90294f6be8eb9310e278c4e121b8a9edc1d8bdac5
- MakerPaymentSpent: 218a4eaa9838c88cc864612ff16422c7b943a1c675252534784048c183060c31
69323b02a2892810aaca08436e7de0c92dbbcd9ad7d1f847b8850f65418cc243
Both payments are on their chains and locked to the same secret hash c0b4de8c0f348e4bfb26cfdb8f03c07c8fa13e55, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c8e6e8d20c85215974b014204491fa869e0c4a69df10ed30958107a9b938ba3f
- TakerPaymentSent · TakerPaymentReceived: 69323b02a2892810aaca08436e7de0c92dbbcd9ad7d1f847b8850f65418cc243
- TakerPaymentSpent: d79fe025a1bea2d3184a2b4ce4500dbf51f1b1aff7569c1e278e168226926113
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.