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.
c0c039a3ef2d5c71a43fd8c4726b85441e851d459f51ad2895958992ce41052d
Both payments are on their chains and locked to the same secret hash cac35ef4b2872b4b5562a9289dfc50b86f7a8810, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c0c039a3ef2d5c71a43fd8c4726b85441e851d459f51ad2895958992ce41052d
- MakerPaymentSpent: 7d6b6c8c7403e9820b618c5a32113c84c8293c5934fe2f3bd123d23fc8e79a9a
f40aa2b533c0626f19899a0556a740a0dae25cd03df0ed7767182c6edcc1a658
Both payments are on their chains and locked to the same secret hash cac35ef4b2872b4b5562a9289dfc50b86f7a8810, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c583871bece0626a0b8baae8a391b940d5c831c2f62709b9ed2946861ccd5f84
- TakerPaymentSent · TakerPaymentReceived: f40aa2b533c0626f19899a0556a740a0dae25cd03df0ed7767182c6edcc1a658
- TakerPaymentSpent: 2d077289bbe2e9e20536bf0a0b549a2d02c1c3921cc44a4bc7ee6bb753e343d7
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.