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.
b8a3f5fd7d5ac8b2302d15087bf67d2c78eb476a49da08715dd23ed470fa177f
Both payments are on their chains and locked to the same secret hash 904c948278df2e64a17861d4fedcf4c46b6f41ad, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b8a3f5fd7d5ac8b2302d15087bf67d2c78eb476a49da08715dd23ed470fa177f
- MakerPaymentSpent: 82b7527492e6d58d141ec2bf016215f4d118d7140f0829faa46b148224ae99be
1f093510e3754fd45df5b1a973f2c5a5a9254a3587b918e8d0919823e99268f7
Both payments are on their chains and locked to the same secret hash 904c948278df2e64a17861d4fedcf4c46b6f41ad, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c54a4c737bce0f18d9cdef663022ba3fa930252d0141a8d1c83de595aa37eb42
- TakerPaymentSent · TakerPaymentReceived: 1f093510e3754fd45df5b1a973f2c5a5a9254a3587b918e8d0919823e99268f7
- TakerPaymentSpent: f6caf1f8033f2e8390f90797792d7c6a8c3d47d9190ef2aca3277d9b76230933
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.