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.
5c547a1eccae669f186b9b5477faa0743b2778cd35b6b81e31d16050b9fda42a
Both payments are on their chains and locked to the same secret hash ffc018454ac1283ab26648af8d0076cc5079f9df, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5c547a1eccae669f186b9b5477faa0743b2778cd35b6b81e31d16050b9fda42a
3601a3939c2a6c6d7d7d39eaeca79b440dfc9d991aa032724c3e59697ff53c0d
Both payments are on their chains and locked to the same secret hash ffc018454ac1283ab26648af8d0076cc5079f9df, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 56d1c4cf43f5d6cd28f755e93be7d547e9d7ab36fd5b7df017ec4d3691252506
- TakerPaymentReceived: 3601a3939c2a6c6d7d7d39eaeca79b440dfc9d991aa032724c3e59697ff53c0d
- TakerPaymentSpent: f9e608e0ac11aa37b6e85989eaa5f7ddf96abf701144f1ef3a7b1de151441cee
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.