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.
981177cb651c54a08a43db55708ac6fd1e6ac5d8667947c72f73de48666e37cc
Both payments are on their chains and locked to the same secret hash df8ddb4229d90d6124d4e817292a85a5852ac35e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 981177cb651c54a08a43db55708ac6fd1e6ac5d8667947c72f73de48666e37cc
- MakerPaymentSpent: a580884f69ac97fa3db9a1d4ba2e8cf40964ca0f4920994b9c435bc97c9125da
f594a80571493c1259a30ad6baf5550e00988137c6fab239c0a38c8bcd150ae0
Both payments are on their chains and locked to the same secret hash df8ddb4229d90d6124d4e817292a85a5852ac35e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5d9530052856f4d7419f8fa39129e51ef28751dba6d313868af07f4033cb7681
- TakerPaymentSent · TakerPaymentReceived: f594a80571493c1259a30ad6baf5550e00988137c6fab239c0a38c8bcd150ae0
- TakerPaymentSpent: e66a91c2b0eb2eec69cad916912ca2fe4b8a42a43f171008fa7f85a39050aac6
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.