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.
3f1a4a625b319cf9ead46cc370b700735eb2856c9b190f05bc1073f73e42a313
Both payments are on their chains and locked to the same secret hash 901fc195ff278504f79850f5edae3ec400a62c3b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3f1a4a625b319cf9ead46cc370b700735eb2856c9b190f05bc1073f73e42a313
- MakerPaymentSpent: 944e2a75e6dff4e67f2944a6296b2d08834fbadda03bffe069538bc0fb4c2376
05791a563538f6d67e9127c0fd63b803d5047685a7f743a9bb7eb3ae54b729d5
Both payments are on their chains and locked to the same secret hash 901fc195ff278504f79850f5edae3ec400a62c3b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b5d9723a3653eae06dc5e7f3c893f83c0af9e63133c358524fe219dccc23b13c
- TakerPaymentSent · TakerPaymentReceived: 05791a563538f6d67e9127c0fd63b803d5047685a7f743a9bb7eb3ae54b729d5
- TakerPaymentSpent: 3e7955f74aa91219e431add53b5b7b6a11ba5ab38369bbbd9e2a0b8a164f2ceb
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.