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.
13108082cd28dbe4578eea0c64f13d5eee5b263ef915563c3fd5b0a1dd45cbd2
Both payments are on their chains and locked to the same secret hash 77a2590e2441a20ad8308ae99d452dae7c860575, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 13108082cd28dbe4578eea0c64f13d5eee5b263ef915563c3fd5b0a1dd45cbd2
6a42f9b80440a2961c168ae34f3b2c6ba319e37d419f29397697d431bd50060d
Both payments are on their chains and locked to the same secret hash 77a2590e2441a20ad8308ae99d452dae7c860575, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: a44623340ce321064611a582435a93a686838812a039e989f16c07a9c749c46d
- TakerPaymentReceived: 6a42f9b80440a2961c168ae34f3b2c6ba319e37d419f29397697d431bd50060d
- TakerPaymentSpent: 0c3f057483b0976c9d6682fb677eba40c4f5312cfc7d77a13d0bec932e24cfe8
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.