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.
ec711b4e065aa7a006595223feb35048b81f6523120d414af298cb1a466c9da1
Both payments are on their chains and locked to the same secret hash 1c813525f5f2e1d94f65b2147322f6e98941fed8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ec711b4e065aa7a006595223feb35048b81f6523120d414af298cb1a466c9da1
- MakerPaymentSpent: bb0c87d7746816d236869ebf1c103f486fa155e9c5188eb09bf538d0325224eb
7cbb104b5ced4b7fb3c92c28d8f247f6cf11d327773b3d417a2d8e0e1dbc1934
Both payments are on their chains and locked to the same secret hash 1c813525f5f2e1d94f65b2147322f6e98941fed8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 05bc5b7ec213a0934f8e222641c01ebcbabd7c75908564938e00659297f1d6f1
- TakerPaymentSent · TakerPaymentReceived: 7cbb104b5ced4b7fb3c92c28d8f247f6cf11d327773b3d417a2d8e0e1dbc1934
- TakerPaymentSpent: dc73517b7a97bf0222b9830c39aa59ea2a9ae1461bba22e3938209c6a3a4ef1b
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.