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.
d01443229c1a5ba5b63ff4a48e804d8fe814cfcfe58c6e9d86fa394fadbfcd6a
Both payments are on their chains and locked to the same secret hash 61224fda4976de9e82e5f0087b8060c819e8455f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d01443229c1a5ba5b63ff4a48e804d8fe814cfcfe58c6e9d86fa394fadbfcd6a
- MakerPaymentSpent: 80f45d3e6a6e6b44c2dfd159bbed3d949e1af8cfb0d1074dcf61f6ede3bf96c8
c69f92243573c43b79fcdcf693239572005258fb369fb93fe2a1d44dfdd10d2c
Both payments are on their chains and locked to the same secret hash 61224fda4976de9e82e5f0087b8060c819e8455f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e88dc17e3f2f964d80472220fe7d802e2733d5d564884d0345bbcd0a1dec5975
- TakerPaymentSent · TakerPaymentReceived: c69f92243573c43b79fcdcf693239572005258fb369fb93fe2a1d44dfdd10d2c
- TakerPaymentSpent: d7585e345d8f6ae75807eaa812a97692c8c37847713ad921445a4331e74868dc
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.