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.
457c3c574032919522b219769be94ec23508bcbfc392cc9dc68d312b04326ce1
Both payments are on their chains and locked to the same secret hash 718a20557682c3ed86ccb2629c9300969d3c0881, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 457c3c574032919522b219769be94ec23508bcbfc392cc9dc68d312b04326ce1
- MakerPaymentSpent: aeec37353b2d5b1c251787aa97df8892b9395659e5a8b5cd6063225588dcf765
6247cad3cb3b81e4370a4bf42db6dee9a52aca51899788a21a74d844c481879b
Both payments are on their chains and locked to the same secret hash 718a20557682c3ed86ccb2629c9300969d3c0881, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8fef7e1aacf4d8a801fba91d2d8684e2e111a409d92fdac2369da9ee7b4f9ece
- TakerPaymentSent · TakerPaymentReceived: 6247cad3cb3b81e4370a4bf42db6dee9a52aca51899788a21a74d844c481879b
- TakerPaymentSpent: 7eba3f95e49d65c3a474add5e26aca75e432faa0bcc51e6f17af5d195eaa5fb9
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.