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.
4731883daa6fd92220d04466fb4970a05cc80439170636cac7e7d7bfa1e1016b
Both payments are on their chains and locked to the same secret hash b6903269ff753d8ef8a6d71c47f207a08de3aa62, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4731883daa6fd92220d04466fb4970a05cc80439170636cac7e7d7bfa1e1016b
- MakerPaymentSpent: 300beb32114eda9e3d9b110bccf6cfa7729bfd12b4e0d7a363878483453ba9f2
2a3213441c63bc1d8ec129c0f822aa42168457c1e7dc1baf5ee80167b5e9e05a
Both payments are on their chains and locked to the same secret hash b6903269ff753d8ef8a6d71c47f207a08de3aa62, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 08d1e9b956f931cf7a5107f292d10401eb1973f607e96dc163edbcd0cb57e976
- TakerPaymentSent · TakerPaymentReceived: 2a3213441c63bc1d8ec129c0f822aa42168457c1e7dc1baf5ee80167b5e9e05a
- TakerPaymentSpent: dbc7f59e9c487ce1fa20e07ae317b659b1fb7f515e4dac914d07aaa29565bec1
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.