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.
73bc4a571ddb9b0b98edbbb9e6178ad52a352636a85f5a819e460c13bbba0e98
Both payments are on their chains and locked to the same secret hash 39760618f04d558839034be79ad067496cf580bd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 73bc4a571ddb9b0b98edbbb9e6178ad52a352636a85f5a819e460c13bbba0e98
- MakerPaymentSpent: 5b29134878ba50335cad73f166a1dcd7e9a32adf4c286c1c0389c7b72c4e9229
49ea10bb5d03e72f9c10bbee4abee2e545a17a5225c819adf4d98f0dafc039fb
Both payments are on their chains and locked to the same secret hash 39760618f04d558839034be79ad067496cf580bd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 030587e26d2789a6f2d1b7abd2715d6f6b09f17cdf50babd591a513791dba63e
- TakerPaymentSent · TakerPaymentReceived: 49ea10bb5d03e72f9c10bbee4abee2e545a17a5225c819adf4d98f0dafc039fb
- TakerPaymentSpent: 642271d2f9a292bde64a3ea1e1f041fb13285d32d0dc7d4ed1b4ac9c887529dc
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.