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.
bd354521d71ddf46e012001b00c74b3f4fe429c75e079c0e0b32ca8a4081cf46
Both payments are on their chains and locked to the same secret hash 394e6033e37a3cae7bd7276f6f8f20d4e51042ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: bd354521d71ddf46e012001b00c74b3f4fe429c75e079c0e0b32ca8a4081cf46
- MakerPaymentSpent: 6739c82b5604ff4314d4abf10c78511447faf698cf95a5d394cdb5cb443944fd
80adcff60ab323d342aa6dc3f49be798dc485dc01f9f9fa24cd32e3c900f5924
Both payments are on their chains and locked to the same secret hash 394e6033e37a3cae7bd7276f6f8f20d4e51042ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3533cb41c9201e5b356b28a49675d46cfb6bacef33c427f4f785f121cf8f47f0
- TakerPaymentSent · TakerPaymentReceived: 80adcff60ab323d342aa6dc3f49be798dc485dc01f9f9fa24cd32e3c900f5924
- TakerPaymentSpent: 300ff8177047fdc85d5cedf6a9c98fafc8130ac6b7d2f17f2c7d8fdc7c174819
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.