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.
4d4e3f2cf6a197d7b294c193a117dbf0d0427098aeeb8b2517db0bdaa00edee5
Both payments are on their chains and locked to the same secret hash 84ae050d073d6adb709a6069edb16c9a3da07d50, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4d4e3f2cf6a197d7b294c193a117dbf0d0427098aeeb8b2517db0bdaa00edee5
- MakerPaymentSpent: 5a3fef1ed4b55a7540d3a9b40e9a70cc66d054d7236a11f0fac4a21d0e43dc6b
2796eb4b50f1873c54c81f33dac8f133436c70217fa87539666544fd82d7c9ad
Both payments are on their chains and locked to the same secret hash 84ae050d073d6adb709a6069edb16c9a3da07d50, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e0cdd2adb23ad990e9deedcc3d026ee414e37ac429e7d2be35d12f82cf8582d9
- TakerPaymentSent · TakerPaymentReceived: 2796eb4b50f1873c54c81f33dac8f133436c70217fa87539666544fd82d7c9ad
- TakerPaymentSpent: 0d1283cffba82c34fd5ea856736e8ece91726f2353a4325ed74077923b2f96f0
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.