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.
f27018b06eaa3e6dd309db9600346d662acea3fee92e029f55e6bb3459705afb
Both payments are on their chains and locked to the same secret hash 2209e610f8d3e37d4bd3c030cabdcd9223dd57da, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f27018b06eaa3e6dd309db9600346d662acea3fee92e029f55e6bb3459705afb
- MakerPaymentSpent: a71840ca78ac3dba24b8617a8b6c3b6572eda473394690fe3357ca9a8b92e045
f466b3381cfa9b3e87de72ebe1e7c483925c58f520397b95ebcf03bb67bbb767
Both payments are on their chains and locked to the same secret hash 2209e610f8d3e37d4bd3c030cabdcd9223dd57da, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c9886a931a7e26dcb8d6f60eee6489e8658691b4dc93204acc4c8c6fa627f00b
- TakerPaymentSent · TakerPaymentReceived: f466b3381cfa9b3e87de72ebe1e7c483925c58f520397b95ebcf03bb67bbb767
- TakerPaymentSpent: d24835912e2ad9180688ce966bb59be6ca48f1ff7fbe263bf0e14a734c4163d5
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.