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.
65d5b60c45652161c80cfcea6cd2161c2357068e69f4bfb31a1fe4aed54d6a2d
Both payments are on their chains and locked to the same secret hash 6a10d21c89f57ce943dcd0839992c61fe4e36f63, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 65d5b60c45652161c80cfcea6cd2161c2357068e69f4bfb31a1fe4aed54d6a2d
- MakerPaymentSpent: 3c379d28e5645f4551738e457f18e867606c458e5a334385a09861b47717971a
036190356721bdf2fa899d102bf2a29e4e342cf160e22248f77ff0a86ae1c43e
Both payments are on their chains and locked to the same secret hash 6a10d21c89f57ce943dcd0839992c61fe4e36f63, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8914c72849fa3ed160405b3822d05851a0e8b58f97800010d421ce174796e066
- TakerPaymentSent · TakerPaymentReceived: 036190356721bdf2fa899d102bf2a29e4e342cf160e22248f77ff0a86ae1c43e
- TakerPaymentSpent: 3990733774ea490e500d42e8a0db257e934568bdc81ea90b0887cc68128b8289
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.