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.
f2510ef869783b2d4b4c3508c4e9b04f75d4c4948d66ad1d279ba3fc502c7c04
Both payments are on their chains and locked to the same secret hash dd92166a5e9b41bc45de225e5c2ce01a946fcb22, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f2510ef869783b2d4b4c3508c4e9b04f75d4c4948d66ad1d279ba3fc502c7c04
- MakerPaymentSpent: 1a19d787c87d462d5bddb4cf2c4fcc295745ecaf4de838b68fab7c7cbe228e76
c1af19676092b16b91e8d3248f4f69a8340cf56d45f135b7f2e5a48910a16b23
Both payments are on their chains and locked to the same secret hash dd92166a5e9b41bc45de225e5c2ce01a946fcb22, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 223f70d8de53eb1feb79c5fe2c56b1ee7bd1f40f7385e0b945e42d8ced33c721
- TakerPaymentSent · TakerPaymentReceived: c1af19676092b16b91e8d3248f4f69a8340cf56d45f135b7f2e5a48910a16b23
- TakerPaymentSpent: 5f430b0fb4348b9c254de36fd84fbecea2eb00f1dbca18552c324d7deca52a88
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.