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.
61c9a3bb38cc9f3500d2d4b01d0ac2b18aa77718262e84dab17b5f97724581ba
Both payments are on their chains and locked to the same secret hash 32cdb5367db4577aae876106ff8302647d3a94ec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 61c9a3bb38cc9f3500d2d4b01d0ac2b18aa77718262e84dab17b5f97724581ba
- MakerPaymentSpent: e84a50cad0bf4179a15fbd4b1a8784ca883cf8c7b151e46b384a49e069ebca67
423fe87baa25027faa94580082f68d1cdaa99366e1b1a938985fdbf24e70d680
Both payments are on their chains and locked to the same secret hash 32cdb5367db4577aae876106ff8302647d3a94ec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dcddc3eefac4974a5edd15f58dbab14b47398a8307250f60eeae319fce5b2b8e
- TakerPaymentSent · TakerPaymentReceived: 423fe87baa25027faa94580082f68d1cdaa99366e1b1a938985fdbf24e70d680
- TakerPaymentSpent: b96d4f7a84777f61b6097fea0122bdc616e1baf676a6fc9a0499b7eb6034611d
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.