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.
48cfd55503462ee8362a8de16b8f5cff80dc118d6e53bb6141b67a1b89cefa9f
Both payments are on their chains and locked to the same secret hash 4f6ef44fe3d54c4f0abf86e8174810d878d0b1a6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 48cfd55503462ee8362a8de16b8f5cff80dc118d6e53bb6141b67a1b89cefa9f
- MakerPaymentSpent: da903f1c35f9414f047973b48f920ed60afbc913a2c76f55463484543eb7b610
73cf6f1cc263f6209fc33d99a09085e3f4aefe41e76fbfc8064192b87f313257
Both payments are on their chains and locked to the same secret hash 4f6ef44fe3d54c4f0abf86e8174810d878d0b1a6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b27534b8c072a17aa2c213f52d3f8e28e81b0d3204b847ec404e0ebaada7449f
- TakerPaymentSent · TakerPaymentReceived: 73cf6f1cc263f6209fc33d99a09085e3f4aefe41e76fbfc8064192b87f313257
- TakerPaymentSpent: 470d259c5472362175989b1b9ae35c9db4e33bc288f4cf7adc281d446c725f30
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.