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.
aa196d2c2c9e20f0d7c646a5ed0738ef246d5d58df01de7d9ddbc6c35e2720e6
Both payments are on their chains and locked to the same secret hash 77a0b5ece5d90e010cf211f6fc4e54cf6bf131bf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aa196d2c2c9e20f0d7c646a5ed0738ef246d5d58df01de7d9ddbc6c35e2720e6
- MakerPaymentSpent: 98ebe5a6b7e17d8820d974872c5498419230225415fe696fb92f0a8836374d71
d9378a719537791718859d056b1f1ae4f303ebba71fbaa0025fca47949fd5bbf
Both payments are on their chains and locked to the same secret hash 77a0b5ece5d90e010cf211f6fc4e54cf6bf131bf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aa114725410f4c12f721149166bd6dc657a90d3141ca30d36e0cf4960510ba02
- TakerPaymentSent · TakerPaymentReceived: d9378a719537791718859d056b1f1ae4f303ebba71fbaa0025fca47949fd5bbf
- TakerPaymentSpent: 40c7a9180aa4eb0a829d99f83385539b07608b767249a5f836ed0a77f21bf7c9
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.