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.
b6f47294c940a61073fa299cb06601df4d86e81532a303a3461b42c11ecaaf31
Both payments are on their chains and locked to the same secret hash 0c83878b621c93fe4738e3812e9ba74f9e0f4f73, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b6f47294c940a61073fa299cb06601df4d86e81532a303a3461b42c11ecaaf31
- MakerPaymentSpent: a5882cbd445959209b3462f1174323fdf6379d8f204140a563977e3f136432a3
2328a34d675705c3980e2f124dc28f6c96e42ce6f27bcf0ce76446de9aabfe9d
Both payments are on their chains and locked to the same secret hash 0c83878b621c93fe4738e3812e9ba74f9e0f4f73, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 994ac360d1023382d2cce6109cf3bc834eb143c6229a2eecfd3429367ac61853
- TakerPaymentSent · TakerPaymentReceived: 2328a34d675705c3980e2f124dc28f6c96e42ce6f27bcf0ce76446de9aabfe9d
- TakerPaymentSpent: c345e385a025f17755f33543f3a720db5ed43ec7fa17a4fa3bf07a9908c06f54
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.