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.
f5ac847239cc809c0e83e35fb7210c96ef6d0a8627fb5ca185f3330d4991a9fc
Both payments are on their chains and locked to the same secret hash 3552bb5da8b204de1e18600612e7e551973fbe3e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f5ac847239cc809c0e83e35fb7210c96ef6d0a8627fb5ca185f3330d4991a9fc
- MakerPaymentSpent: e9a633f58183d6a28bd7ca6f415ecf4b0eb16f22baa83146b234a3549d3129b6
7aea3c984ec4893f5161fda8ef598781bb00e7b7625e344fecc141c0b7dfcc2c
Both payments are on their chains and locked to the same secret hash 3552bb5da8b204de1e18600612e7e551973fbe3e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 497af0a620b60fbeb66a7a21d2a3459ade916b413e36023bcd3ed0a2d28c878f
- TakerPaymentSent · TakerPaymentReceived: 7aea3c984ec4893f5161fda8ef598781bb00e7b7625e344fecc141c0b7dfcc2c
- TakerPaymentSpent: 50c2b6b7d4be20c8a133be97627a9b4a44215fa2e1ffb34abdf4870595546446
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.