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.
07a0dedeac98e7cfcecc6e2e09814f0818aedade83a3305a3ee5b54493ad31e5
Both payments are on their chains and locked to the same secret hash b79f47cd51241efbd210fc9be16b4491c24acbf3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 07a0dedeac98e7cfcecc6e2e09814f0818aedade83a3305a3ee5b54493ad31e5
- MakerPaymentSpent: 5f3cbf2107ba5b86ea73407280c1d0ab71200701d6f1f81d0a800c363c788cfe
6a6811e722ba7e434629d3de91444dd5fa34128de617dc062d6e9db87dd1aba3
Both payments are on their chains and locked to the same secret hash b79f47cd51241efbd210fc9be16b4491c24acbf3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 563223e79c743d1f03d855031b7141f64000efaecbb996ac0909486e6d0a01dd
- TakerPaymentSent · TakerPaymentReceived: 6a6811e722ba7e434629d3de91444dd5fa34128de617dc062d6e9db87dd1aba3
- TakerPaymentSpent: 1629250f39de148c5efe29501f2dd71606c7cde18354b3a053985b152175a892
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.