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.
d2c4be04d9a603dcd14fa9578d6819b20f53ce5254308f031d5c515b7694d71d
Both payments are on their chains and locked to the same secret hash 91c2d827388c8858204f668386f6ddf2238484a0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d2c4be04d9a603dcd14fa9578d6819b20f53ce5254308f031d5c515b7694d71d
- MakerPaymentSpent: 0d8c95eec17a1340b44c5b58eca8aae9b63ef3d8425dd443c2c07b31dca3716e
7c2c350e86801792eb681eeda710cf4f9394e3204be4b6671113ff13c858b29f
Both payments are on their chains and locked to the same secret hash 91c2d827388c8858204f668386f6ddf2238484a0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8f0c5ac9b79b3782b520107d76bcf6e8c293d20ea69ab4a8bcacb58b27c608ff
- TakerPaymentSent · TakerPaymentReceived: 7c2c350e86801792eb681eeda710cf4f9394e3204be4b6671113ff13c858b29f
- TakerPaymentSpent: 1fdcd687a858f5b778fcc6e14aeda15108e601e05a97d9bf3b32bb74409d66f8
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.