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.
fa30c726876d4abc391ca36688903a00bb40f8f0b5bdc29ca2b123f3efc54f9b
Both payments are on their chains and locked to the same secret hash 1bc70621145ee82bb47088172eb134687bf8960a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fa30c726876d4abc391ca36688903a00bb40f8f0b5bdc29ca2b123f3efc54f9b
- MakerPaymentSpent: 2902b37dde737ff655eb72e05f00b67a6a90b7a2d934f3b8e0980f10de138da4
c99520ddb7a39124ef352956fe5b3cc067eb81051eb0de4d259694ec5d0b9cc3
Both payments are on their chains and locked to the same secret hash 1bc70621145ee82bb47088172eb134687bf8960a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 07eb71b42c17f16646c91a117db3c528bc620088862edcb20f49091e146fc26a
- TakerPaymentSent · TakerPaymentReceived: c99520ddb7a39124ef352956fe5b3cc067eb81051eb0de4d259694ec5d0b9cc3
- TakerPaymentSpent: 676f3968896a6da5db74c34a748de5fada80f89f97d0648ad4d08a023c5900aa
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.