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.
ba804bca198b15b2619724d1cba2f2c4bb482cb371a339a6a88b6c20d98a59f7
Both payments are on their chains and locked to the same secret hash 7c676d6b677ec2e74b5401e44c94e481b39bbd21, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: ba804bca198b15b2619724d1cba2f2c4bb482cb371a339a6a88b6c20d98a59f7
478662015f9f8c8ef1b9d1819d52001e7b1398e39314647154500aee7583c41b
Both payments are on their chains and locked to the same secret hash 7c676d6b677ec2e74b5401e44c94e481b39bbd21, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 8defae01f0bac0de43cdebb137f34088ff3366c0ee8a409489fddd0f988f3bd0
- TakerPaymentReceived: 478662015f9f8c8ef1b9d1819d52001e7b1398e39314647154500aee7583c41b
- TakerPaymentSpent: 83d4ef8479534d91bf1fe4e849d0df245b7a81083c1054f1b92946834c389761
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.