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.
2450667ec1494b81e0afc5f03d6a768957a6c40d12b902615f66eb7c93cb5024
Both payments are on their chains and locked to the same secret hash 68be28089881df632e83f305c12caa91d63b93a9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2450667ec1494b81e0afc5f03d6a768957a6c40d12b902615f66eb7c93cb5024
- MakerPaymentSpent: a8c2bd3c126171ad24760122b47c90b7ae5199e757c09959e47e1b063e50125a
779c463b368ff3346ecd9a68e957671d877992f7710d7d143fd305795a0b2000
Both payments are on their chains and locked to the same secret hash 68be28089881df632e83f305c12caa91d63b93a9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6becaae57cd99398654d374d79dc9367386ecd53848d7c95895710fff35aa4e4
- TakerPaymentSent · TakerPaymentReceived: 779c463b368ff3346ecd9a68e957671d877992f7710d7d143fd305795a0b2000
- TakerPaymentSpent: b48d99b64d3dbd12daea72c140b2f175d2cc07abf2fab8ef1a716cbb9ef23a19
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.