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.
4fc3f373cb0d130d9744a135bf2e8aa6c7ad252f52d53f7377fe02323989c63d
Both payments are on their chains and locked to the same secret hash c93162fc444cc49c56a9ca255eb9aaa194117bea, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 4fc3f373cb0d130d9744a135bf2e8aa6c7ad252f52d53f7377fe02323989c63d
fba9ac820a1e1fc51cfbbe30e37b031bc3b969d72549d245bf5e64f0e1bb17f7
Both payments are on their chains and locked to the same secret hash c93162fc444cc49c56a9ca255eb9aaa194117bea, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c0e5027d9a85cbd94f5ee9eb8114c64bd59307c929beb6bf385e44d43b08ed40
- TakerPaymentReceived: fba9ac820a1e1fc51cfbbe30e37b031bc3b969d72549d245bf5e64f0e1bb17f7
- TakerPaymentSpent: 4b872f00c53701bed849808dcef4ab034a85fae73e2bede606054981fed265f3
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.