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.
3e267d4119acf28ab14e2de76338ce847fe71d2602372660dea874baa5b89044
Both payments are on their chains and locked to the same secret hash 2d028d3ae4e48e4a7af19e71f6d98cdbd1ef5fa7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3e267d4119acf28ab14e2de76338ce847fe71d2602372660dea874baa5b89044
- MakerPaymentSpent: c861796d14d4637f3417d086197f5ae5461485ac9246508da79d1544b1a8ecaf
fcffef6a113812b257a9fea19a160069fc81a819fc461b1f60588953242bcd6a
Both payments are on their chains and locked to the same secret hash 2d028d3ae4e48e4a7af19e71f6d98cdbd1ef5fa7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5823cae04921d4e92ff5523cbfabba7f0ada490ac103484167caf025af3a7e8f
- TakerPaymentReceived · TakerPaymentSent: fcffef6a113812b257a9fea19a160069fc81a819fc461b1f60588953242bcd6a
- TakerPaymentSpent: fcc4847bf92cf09bcb97fa927a2e901a7e086992176e13ef22a9cbf7a772968f
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.