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.
ffce351f456e5c8bcd69d3e105c0b9b5a2fd8560aeab94bc79491bb9ec092519
Both payments are on their chains and locked to the same secret hash 949344da0ddf5ddcdff96b546a3c1e98001be3da, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ffce351f456e5c8bcd69d3e105c0b9b5a2fd8560aeab94bc79491bb9ec092519
- MakerPaymentSpent: 5d1a315e3415822630dcd82f33fa9c36fcdb4fcf47223d72d00a717d36b895d4
1bf967d2cdc4b5d225f563022d33941243340e82d93e44cbd60f7178ad9a4107
Both payments are on their chains and locked to the same secret hash 949344da0ddf5ddcdff96b546a3c1e98001be3da, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1372c0193dd2ab2c4df131d1d68c27521c0279c63d87ec526d54c813587baf0c
- TakerPaymentSent · TakerPaymentReceived: 1bf967d2cdc4b5d225f563022d33941243340e82d93e44cbd60f7178ad9a4107
- TakerPaymentSpent: 488baad19617e11eb53b1281998eb369b5cb454aceee1578f4c36d66406a0fe1
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.