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.
db7f6e466bfb22f3f86cefb7caf9468fc0a62636b690e5cfcf15fe7894c51090
Both payments are on their chains and locked to the same secret hash 259f34c0fd467c1eb592e7731a39cb2a7e971df3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: db7f6e466bfb22f3f86cefb7caf9468fc0a62636b690e5cfcf15fe7894c51090
- MakerPaymentSpent: a40aa49420ebae95d7c3a9993dbfa46cf1a1f283943bbfe8f5be23981c30dcb5
6c954c0038139298e410fd910d1b6ec06f14da8f9c338eed3848c9d6f7cdcd03
Both payments are on their chains and locked to the same secret hash 259f34c0fd467c1eb592e7731a39cb2a7e971df3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5b2519d67b3aa13ee3ddb11f43598dd6a212b3c64524c343262c8813fc71a63a
- TakerPaymentSent · TakerPaymentReceived: 6c954c0038139298e410fd910d1b6ec06f14da8f9c338eed3848c9d6f7cdcd03
- TakerPaymentSpent: fd667d1788aee7f94467f2369cd6b9affb1ade8ab69e0a4f3f6329e4f4ca912c
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.