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.
b56cfc4a7c351dcf9373193fafc0bf57efc9c64bf8e3d3fcae190ca364e25794
Both payments are on their chains and locked to the same secret hash 1ca025254c8fce6b86a001fb0d7bd97cda26211e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: b56cfc4a7c351dcf9373193fafc0bf57efc9c64bf8e3d3fcae190ca364e25794
e8d29e4f151c4cdb00437ff9de88238df3588a05b944d7c66d67669bfc8ee974
Both payments are on their chains and locked to the same secret hash 1ca025254c8fce6b86a001fb0d7bd97cda26211e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 70cf78cc60555bb64a031c54452081d709f5d6a8050ed35b89ce1dba71b15130
- TakerPaymentReceived: e8d29e4f151c4cdb00437ff9de88238df3588a05b944d7c66d67669bfc8ee974
- TakerPaymentSpent: 0346829de32e5cc50bb0626504f2445bece5a4483581329d46e5efe9462578f1
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.