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.
a4f4e338b80f43bfea3ab1c523d2c014f9bf454aef8b11fa0a43e422495f2263
Both payments are on their chains and locked to the same secret hash 886f1c966ceb7bc08214e8bfb1183f5ecb006b9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a4f4e338b80f43bfea3ab1c523d2c014f9bf454aef8b11fa0a43e422495f2263
- MakerPaymentSpent: 9924fb2ab7e630bc263c5a44f38fefee7888b901f36117246f030d78b37ee28e
529f7722a8cc18990eaf1b9c74aa6f46e47ef0e24410947405e286e7559167e5
Both payments are on their chains and locked to the same secret hash 886f1c966ceb7bc08214e8bfb1183f5ecb006b9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 88c9b01ad51ff976f022250fc45f3ec58b8f706bf576dcb214a83ddd790f45bd
- TakerPaymentSent · TakerPaymentReceived: 529f7722a8cc18990eaf1b9c74aa6f46e47ef0e24410947405e286e7559167e5
- TakerPaymentSpent: ade15d5bdaeb40703819bb83895cd02e6d33b6753d7538e4a541aa26d7fdb6c8
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.