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.
3816d8828946285f91ca98343564e9e0e1c5e70ce3db31476f0fa450ece3ee58
Both payments are on their chains and locked to the same secret hash 37a4f234998de114d0ffc126293fba5331a22bc1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 3816d8828946285f91ca98343564e9e0e1c5e70ce3db31476f0fa450ece3ee58
51badf2e3c6187eef087cefd4d1b72669d73abeba3e8343f4b2268a7ae8269bf
Both payments are on their chains and locked to the same secret hash 37a4f234998de114d0ffc126293fba5331a22bc1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 29b7a3c7bdf164e734021809ee5c54de7ba24917d8dd01a26b7bcdc392a54561
- TakerPaymentReceived: 51badf2e3c6187eef087cefd4d1b72669d73abeba3e8343f4b2268a7ae8269bf
- TakerPaymentSpent: cf0a1aee38e46c2790fd5f18c9fd0e4b1b4d184ef2a27e4f3f22ee348847294b
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.