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.
f263185bc8edc17f0e9080ecd75428eee990d672f00ee703c80c2346b395bab0
Both payments are on their chains and locked to the same secret hash 01a42ba82ffe883558ea60761eb4ab4e5c5d64f4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f263185bc8edc17f0e9080ecd75428eee990d672f00ee703c80c2346b395bab0
- MakerPaymentSpent: c6de7c67176f8e269322c0fd7c861790152aa489e39801abfed90869eabeb037
9322eda53ff0f0811d112020fc98e566d83b02d01e7b0f969aea8633c272e566
Both payments are on their chains and locked to the same secret hash 01a42ba82ffe883558ea60761eb4ab4e5c5d64f4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a4ef9fc5fe03263addbeb4d0afd9c758e795ec761c49c8342ecb2fc40688e18a
- TakerPaymentSent · TakerPaymentReceived: 9322eda53ff0f0811d112020fc98e566d83b02d01e7b0f969aea8633c272e566
- TakerPaymentSpent: 3458639585cdf73dd15abacc3c5d5583bfd0a11f936bcbfabd93df063174e924
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.