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.
5a5fbf3fcf11ccd2d55abb3de0662895d442a0d2c9b7baeff01b9227ce1e92d7
Both payments are on their chains and locked to the same secret hash 101486d9427327d76c4f38d08578b5078a03bcd6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5a5fbf3fcf11ccd2d55abb3de0662895d442a0d2c9b7baeff01b9227ce1e92d7
- MakerPaymentSpent: ef1c5033c54da290a62f867bdb92fae78d17c65e2159f176566c0d07d47468e9
2b12bf4f7578fb64939bd391684ee84447dc2eaab8d2a148d2ab23e54a5ca331
Both payments are on their chains and locked to the same secret hash 101486d9427327d76c4f38d08578b5078a03bcd6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b11ac2fb5a5038b1d7b0ddfb504235dfa89ef57c98088be57833af07bf0a220a
- TakerPaymentSent · TakerPaymentReceived: 2b12bf4f7578fb64939bd391684ee84447dc2eaab8d2a148d2ab23e54a5ca331
- TakerPaymentSpent: dcf6e4d09882120052721dbac654e17cac8e62caeeb244fbf5ed1331d6658d40
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.