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.
9b7fead6059fed6dc1a53cb3c43fba66cd1983e4f30b4c9aa48e43c372bf29f1
Both payments are on their chains and locked to the same secret hash f2544b47030fc5df8f478aea9a7c44c55fd7fd54, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 9b7fead6059fed6dc1a53cb3c43fba66cd1983e4f30b4c9aa48e43c372bf29f1
- MakerPaymentSpent: a6dac4b6886ef7388fe5dcf232a01d1e11d0f29831246d9f48595dc9ce515971
9b81a2fdb781007cc3fd14544e8248ecb3877b14e9e9867a34d836455840ed11
Both payments are on their chains and locked to the same secret hash f2544b47030fc5df8f478aea9a7c44c55fd7fd54, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a661846926b79875928c224e8b6463da5ea046fc9fe7bad1f89b7cea898a86d8
- TakerPaymentSent · TakerPaymentReceived: 9b81a2fdb781007cc3fd14544e8248ecb3877b14e9e9867a34d836455840ed11
- TakerPaymentSpent: 6f9d01a7345694b4a16aa36ef2faea44c331b459b9e5bbb780c2d000dd8093c3
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.