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.
88e6aa7abd4f61629857ea957fe9bafa75e731968f1ba400c13aaae08b4fea40
Both payments are on their chains and locked to the same secret hash 5526e0798e58f2fedd0e2059f018a2a78c5d9d92, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 88e6aa7abd4f61629857ea957fe9bafa75e731968f1ba400c13aaae08b4fea40
- MakerPaymentSpent: 79386826443c4dad2610e8ceba38054deda678bdf3ebacfb7b2b20f80da23d49
f86643d8ed5c22a8e10a65da4cc5a400d2b4a01a28337beec65ed0e2fded489f
Both payments are on their chains and locked to the same secret hash 5526e0798e58f2fedd0e2059f018a2a78c5d9d92, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 591ca428511c8b102e57c29cc0be1443fedd04179af07b8b1643f145b452e88a
- TakerPaymentSent · TakerPaymentReceived: f86643d8ed5c22a8e10a65da4cc5a400d2b4a01a28337beec65ed0e2fded489f
- TakerPaymentSpent: ace0dd9715fe70e72acafed2987fa9fea559674edd320697de24e77e52912932
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.