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.
329b1f317cf59539d5ec55131352d0fd1cea06081ad5990ee097973bb4f353ac
Both payments are on their chains and locked to the same secret hash 3df07300f81f66a682a2cba729064bf2439825d8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 329b1f317cf59539d5ec55131352d0fd1cea06081ad5990ee097973bb4f353ac
- MakerPaymentSpent: 13f9496a488fb8deae04023f21dcdd54202eeeee8cb3c13918d864b6b46d16ad
dc1bdec8e96ef504f8c547871b3fa861ccc01ed01d8a5306f677fe997380e512
Both payments are on their chains and locked to the same secret hash 3df07300f81f66a682a2cba729064bf2439825d8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 528ed7d357bd4006a2b6786a33f5053c46e16d5ab1a885d6160a0db5bedf83aa
- TakerPaymentSent · TakerPaymentReceived: dc1bdec8e96ef504f8c547871b3fa861ccc01ed01d8a5306f677fe997380e512
- TakerPaymentSpent: 5c51ba7e3958019539eea393e46a3f1836901167b9ed9365be836918868f3b5d
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.