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.
61eb66c52f7926459ab42c84758f2541c920b01fa14f4322e450687b72d2400d
Both payments are on their chains and locked to the same secret hash 55c72b16c9264c4834fb161e03e50e95fe34361d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 61eb66c52f7926459ab42c84758f2541c920b01fa14f4322e450687b72d2400d
- MakerPaymentSpent: b118c6c14febc0668854ba98848cf6923190eab543e92c263279b6afc0a2adda
468c373c915d634a8200d118b6736b867b6cfa37799c8a33b3d11ae9c7a35ba0
Both payments are on their chains and locked to the same secret hash 55c72b16c9264c4834fb161e03e50e95fe34361d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 731b98be04ece96eb64e15c93e3267d3b44e6808e66af77ff39a33bdd8af5a8f
- TakerPaymentSent · TakerPaymentReceived: 468c373c915d634a8200d118b6736b867b6cfa37799c8a33b3d11ae9c7a35ba0
- TakerPaymentSpent: 6fccdcc7a75734399521479d39f41160c6ef1b940c3484a1cda89dbbac70e34e
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.