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.
9f5eb691d135504ea02a124f30a29d51d6c585c918a6f23c47203d279cfa3bbd
Both payments are on their chains and locked to the same secret hash a4fe87744c4159d68b4f6fdbc1722f43cdf13135, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9f5eb691d135504ea02a124f30a29d51d6c585c918a6f23c47203d279cfa3bbd
- MakerPaymentSpent: a120cba41302282c51435b676cfc3fcd3884dc60bb4838599cd42b397cde8d3b
f1978cf9d125270ee38131d90880943ca4803d4404abeafb36ffc52ecee77631
Both payments are on their chains and locked to the same secret hash a4fe87744c4159d68b4f6fdbc1722f43cdf13135, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ba70339e739ab01c44366ef6204807fc7b2c51b02ed83b4628bd1d6230f01ab9
- TakerPaymentSent · TakerPaymentReceived: f1978cf9d125270ee38131d90880943ca4803d4404abeafb36ffc52ecee77631
- TakerPaymentSpent: 201acb5bc33016a4aaf646e13fa12c2c6cccafca39e645ff9a9997e2a3f55c88
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.