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.
3a0181995e6310b85bedee78835fe56052edba5059c915badbd9913d90bbd606
Both payments are on their chains and locked to the same secret hash 78f5e4b39faabaec3cc8f73fa33f368c6949559e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3a0181995e6310b85bedee78835fe56052edba5059c915badbd9913d90bbd606
- MakerPaymentSpent: 030d042165f708a95dc13cfebd78ec5a7cd239fee44b99dd1563ca4cdc284ca4
da211f0e40d6b7cb7dc3edf1662425f976c5e2b1f464a8660a05a258ba9a945e
Both payments are on their chains and locked to the same secret hash 78f5e4b39faabaec3cc8f73fa33f368c6949559e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 19fcff86ed62b2212aafc5642eb940375ba8d5adf9cc0a91b8c8690141d37e07
- TakerPaymentSent · TakerPaymentReceived: da211f0e40d6b7cb7dc3edf1662425f976c5e2b1f464a8660a05a258ba9a945e
- TakerPaymentSpent: 1ac87183c999d38f74c1591ff84e8bd226d410439b45c8489a24ba483187eb61
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.