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.
b4857ccf48b7a0fef98ce527adea9c55d1186bc5ecb21f13192150df98e2e99e
Both payments are on their chains and locked to the same secret hash 19102e05082a221d62c0058604518955eabbc301, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: b4857ccf48b7a0fef98ce527adea9c55d1186bc5ecb21f13192150df98e2e99e
d22944a5349aa70820c57a99cc308da0cf6a4550337737a5523b831d47caa802
Both payments are on their chains and locked to the same secret hash 19102e05082a221d62c0058604518955eabbc301, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 8d4ea1e4b7ba6b24a0600aff48ae5c50d43b8d6dae443c4df0959f81d3a29ec4
- TakerPaymentReceived: d22944a5349aa70820c57a99cc308da0cf6a4550337737a5523b831d47caa802
- TakerPaymentSpent: 6c70a9edecf53aaf0178838181578102cba8a5705223a32c4e48e1a0b1958fe7
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.