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.
3335c303275650a319942e51f2fcd695f70ae24f61ad5b551c3e90bdc1362e03
Both payments are on their chains and locked to the same secret hash 3e0599633fc808b731f9a58ae4f04139f090f2af, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3335c303275650a319942e51f2fcd695f70ae24f61ad5b551c3e90bdc1362e03
- MakerPaymentSpent: 9ee9af54c874065a817c8cf1136a38852da46bb0189f5147221eb479b62b96a8
f0b0a1b893a28ea58798febd87cd6249ba36fa11d8b1412cda7943f289de2e4e
Both payments are on their chains and locked to the same secret hash 3e0599633fc808b731f9a58ae4f04139f090f2af, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1ea00b4f48f86aa35038ab90a7f32620f88e4833814d26a9cca76aa76758169c
- TakerPaymentSent · TakerPaymentReceived: f0b0a1b893a28ea58798febd87cd6249ba36fa11d8b1412cda7943f289de2e4e
- TakerPaymentSpent: a8219a568141453733c736c96488881c492a8f3f9939a01f9172fdb60152c83f
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.