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.
e2a5bc7e5ed11e64b50c78705756fc249653c1a397ef0d733e41a128b8d9339e
Both payments are on their chains and locked to the same secret hash 24e02d9a86c21f2cd6a405c0a56c9ec46c6e83bf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e2a5bc7e5ed11e64b50c78705756fc249653c1a397ef0d733e41a128b8d9339e
- MakerPaymentSpent: e544cb22beed2a5e1a0c1fcfed635c41fbb76495b2e09f254037e7c1cd8c4b21
e199146e787f200caf542453f3f6a3507537e3406926f4ed3f20cdf8ebb7401e
Both payments are on their chains and locked to the same secret hash 24e02d9a86c21f2cd6a405c0a56c9ec46c6e83bf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9d1e99860c0dd55f0801789f8cba442028e1e49896159dbc31ea268e02d92cb9
- TakerPaymentSent · TakerPaymentReceived: e199146e787f200caf542453f3f6a3507537e3406926f4ed3f20cdf8ebb7401e
- TakerPaymentSpent: d6f092d803e6e048fa2df24c3b5e0f746552b8813d417619c58ba336a4ea69e4
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.