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.
c46e6a1aa7c0774f6b9c8ac828b63c7e8e71ab345e75fa2726949d605750b296
Both payments are on their chains and locked to the same secret hash 3a11f3c3dca7adb9d81a86291e29ff514dbb3227, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c46e6a1aa7c0774f6b9c8ac828b63c7e8e71ab345e75fa2726949d605750b296
- MakerPaymentSpent: f5b795dd44d4ff09174a510d9609342044ea7d69e9f6481a539dd4234642e6eb
96f8f7c63d41e5e0fdc0439e03a5dcbd29d046aebe9294be4b3f611f7e133654
Both payments are on their chains and locked to the same secret hash 3a11f3c3dca7adb9d81a86291e29ff514dbb3227, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e0700965e85eb1bcce1da8b6cdb6cb03e347d49bda1adbb315ea9d5344bcf043
- TakerPaymentSent · TakerPaymentReceived: 96f8f7c63d41e5e0fdc0439e03a5dcbd29d046aebe9294be4b3f611f7e133654
- TakerPaymentSpent: 44dcdf4f0a5f6d696e2d74efbe63867f5a68e2c73d3f8ea1f99642d8c1f53bce
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.