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.
18fd5410c1036525ed66ced1ea2829b1b2b854fdaebe593703b7f215e5d9fbf8
Both payments are on their chains and locked to the same secret hash 2bba91523d971bd4e7c208ad0f7115c9bde542e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 18fd5410c1036525ed66ced1ea2829b1b2b854fdaebe593703b7f215e5d9fbf8
- MakerPaymentSpent: 0a2fd6cc131c48e4befc649c11be830ec8efac377ea14bd988be38ce396fa3e3
3f68f3b74d8b7a7d32915f4262be364a9e1417317e1cbd168dcb2c405cc6d222
Both payments are on their chains and locked to the same secret hash 2bba91523d971bd4e7c208ad0f7115c9bde542e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b3e68dacc68c570b5106e16de55f89d250c55e1a745d36d4de2c8a0cd47d3670
- TakerPaymentSent · TakerPaymentReceived: 3f68f3b74d8b7a7d32915f4262be364a9e1417317e1cbd168dcb2c405cc6d222
- TakerPaymentSpent: 29fd78719995a909a196f32fe6ca132fb4c08c9684dd67d88e45b630bd392ab4
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.