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.
517e6071f64dd735b318cef8f66ca452ac9dbf107d461855e8db4a1f3974c3e4
Both payments are on their chains and locked to the same secret hash 8399325027bd3b2ee0d80d117e735f6a3144180e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 517e6071f64dd735b318cef8f66ca452ac9dbf107d461855e8db4a1f3974c3e4
- MakerPaymentSpent: 361dbee877e9f7359d6dd2b9af35b56a8b5fb8535d4aaff6d4667d5d497ec49e
0f2fd9b362ec70fe1f4adecb7f20007315de3c57b154800af06f6d5dc197bfeb
Both payments are on their chains and locked to the same secret hash 8399325027bd3b2ee0d80d117e735f6a3144180e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: d5d335761f93da5146e4e69e995dff1ca55515e19f61b53de8275f2c1eac8c1b
- TakerPaymentReceived · TakerPaymentSent: 0f2fd9b362ec70fe1f4adecb7f20007315de3c57b154800af06f6d5dc197bfeb
- TakerPaymentSpent: be92fdc9520f003bd3e85a5306b46ad9a0a6126a49c649b4910a70eef9c829a4
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.