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.
767d0e5ab047655a8c12834d983e09258f60f718500d145156b25fa321a21125
Both payments are on their chains and locked to the same secret hash fda84b870503ef140521700d094011b0b592da02, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 767d0e5ab047655a8c12834d983e09258f60f718500d145156b25fa321a21125
- MakerPaymentSpent: 7b19ac2807ce618ea6c8d3901cd313ad93eba77c6075b88a0587961c7436e197
6335388c84b16f44079bd92cd8303637ecddc64b85a15db23bf75baeba9cc083
Both payments are on their chains and locked to the same secret hash fda84b870503ef140521700d094011b0b592da02, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c3e4ba391198c967260d0c79829d928620c9b21a63a8ce7c1f6a19503d699541
- TakerPaymentSent · TakerPaymentReceived: 6335388c84b16f44079bd92cd8303637ecddc64b85a15db23bf75baeba9cc083
- TakerPaymentSpent: 17fefe576048ca76b63e0e7b2c3b318ad4a3e6c7b9eaef304756b2288b13f5ac
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.