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.
932ef0b41a82fad502868810d29379206b4737ba596735ec2fca2dc9a49fde93
Both payments are on their chains and locked to the same secret hash 22f2153c5ed8caae0a81f54a8d26d68604a626d7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 932ef0b41a82fad502868810d29379206b4737ba596735ec2fca2dc9a49fde93
- MakerPaymentSpent: 3667465810a14baf543ae9a74d81a9fbd4a1f17ab8c014ac249d75247486287f
8b30ee041292053344ae6ab2ae37063cff983c32c6a68de4c8cd224da30c7926
Both payments are on their chains and locked to the same secret hash 22f2153c5ed8caae0a81f54a8d26d68604a626d7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3a7f9145168319eaeed12bad5db14354799eea474f11779000795e3835034c0f
- TakerPaymentSent · TakerPaymentReceived: 8b30ee041292053344ae6ab2ae37063cff983c32c6a68de4c8cd224da30c7926
- TakerPaymentSpent: 3fe753473612ef132657e636ec7afe1cd3c8072bbca560b4875062cae57e46ca
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.