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.
3185a74deb5ff43bb3d48d6de784e7cce2b4cfd83a94b61a5a08f66fdf8fe101
Both payments are on their chains and locked to the same secret hash 693e80f38b2d0cb5b9d5b435f88d7af99f2f6db5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3185a74deb5ff43bb3d48d6de784e7cce2b4cfd83a94b61a5a08f66fdf8fe101
- MakerPaymentSpent: 153083fd94f6a5639b5e9652db20bbddc2591ebdd2a82f0c3e1903be15f6eb33
59b8252a7a1f87553f048b6b7caf31e2084ac3ab0b3954feece9ebe37323d1a6
Both payments are on their chains and locked to the same secret hash 693e80f38b2d0cb5b9d5b435f88d7af99f2f6db5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3d2045f9baaea49f27228e7d47fe4ac2bc37e778d4572c8cb23f810b447f659b
- TakerPaymentSent · TakerPaymentReceived: 59b8252a7a1f87553f048b6b7caf31e2084ac3ab0b3954feece9ebe37323d1a6
- TakerPaymentSpent: b15bbb1c3516f5f1384a9bc4dadba41e0dcc414dd824f3f4b2dd4a00f175088b
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.