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.
577ae5211b81e1c46460c0cd809a14cee1c9116c1483e410c6a8fb0e922d5f23
Both payments are on their chains and locked to the same secret hash 488a95f8baa3b46885d67e09f54453f8a71d2ccb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 577ae5211b81e1c46460c0cd809a14cee1c9116c1483e410c6a8fb0e922d5f23
- MakerPaymentSpent: bf566e32dd8412a1905c25b20908077cc1a2654f64b901ca3eb0b882d464b8c9
abc8a5fcc2c3610e3486f5b1fba5b77c28cf6dafe137ffc77b54a245a15921ee
Both payments are on their chains and locked to the same secret hash 488a95f8baa3b46885d67e09f54453f8a71d2ccb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 6e82cbe8086b0c8d6329ab5913fe49e8dcc637bf3c43bb72d9a167592acbeee6
- TakerPaymentReceived · TakerPaymentSent: abc8a5fcc2c3610e3486f5b1fba5b77c28cf6dafe137ffc77b54a245a15921ee
- TakerPaymentSpent: 223754351e04b9a6b3344d1a0955526b4d3fe8e5e4ed353a46d60d038fd23d95
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.