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.
c71b20de6ebceaeff1bca63e89014379741b85921993765b34d7c4e7a60f9a01
Both payments are on their chains and locked to the same secret hash 6f5ca7d476fda8c3c1a1d6489ba5b16a1f2d1d0d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c71b20de6ebceaeff1bca63e89014379741b85921993765b34d7c4e7a60f9a01
- MakerPaymentSpent: 910c44e5e8b3aabbce43a706f2728192279fe668f21d3b53b061efec19ea3d08
90a287e86c986290cb3a082cd81ef315afb51f506d3232fcffe06d4ae7951c87
Both payments are on their chains and locked to the same secret hash 6f5ca7d476fda8c3c1a1d6489ba5b16a1f2d1d0d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 35bc0f11a19d225163e12a02cf318f246e0547ff3015a982a86363384c8da535
- TakerPaymentSent · TakerPaymentReceived: 90a287e86c986290cb3a082cd81ef315afb51f506d3232fcffe06d4ae7951c87
- TakerPaymentSpent: f02e584306a5729e19087152a96c535d29abc71c0e3d5d9669cd6c34b82f2a3a
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.