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.
9a4b1b2d4fcf6b2398d057dbb4f6467e6753ca743853c0442444abb893783e12
Both payments are on their chains and locked to the same secret hash de3622ec89691ce6d9c99ce1c7e550f45393cd5e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a4b1b2d4fcf6b2398d057dbb4f6467e6753ca743853c0442444abb893783e12
- MakerPaymentSpent: a94460d84e25ac195f4837b8e1909a888caac6cbbc6fc9365e4d005c2a6c6cda
3ebc3cda363ce36dc55d770fcb69b999507b918124061d3fae069b26f116d639
Both payments are on their chains and locked to the same secret hash de3622ec89691ce6d9c99ce1c7e550f45393cd5e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e96b46ac3979ddbb083ea616854ed361af0a280fecc5244f26d894dfacaf7383
- TakerPaymentSent · TakerPaymentReceived: 3ebc3cda363ce36dc55d770fcb69b999507b918124061d3fae069b26f116d639
- TakerPaymentSpent: d5873b0a59b148a38924cb16866c59edb5b2402253882f15c1c6518acdd4aac8
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.