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.
644c534b1c89d1906b9b827c0e9c76e0bdb69166bb41c43f15e5057310881dc2
Both payments are on their chains and locked to the same secret hash ee5159158ca4b4a507e15a8315773e3f80537412, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 644c534b1c89d1906b9b827c0e9c76e0bdb69166bb41c43f15e5057310881dc2
- MakerPaymentSpent: 17e0ac67cc09eadf30b6b0cb921dcfd74d09ada92f4a2270cdb4f03d1058d3aa
a82bcdc9a83244471ad9a1c4a2f8de04c198725131272c69f92e2894bad221e7
Both payments are on their chains and locked to the same secret hash ee5159158ca4b4a507e15a8315773e3f80537412, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5cfd5f3fe832e55d7743c4d5a0e8e8c733c6e6c36a5b1f9ded42ee06840a1bf3
- TakerPaymentSent · TakerPaymentReceived: a82bcdc9a83244471ad9a1c4a2f8de04c198725131272c69f92e2894bad221e7
- TakerPaymentSpent: 0a417714d4fb3d2475d3a6f956b24c94e891b3c5f5ffc68bccf58f568445e4f5
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.