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.
10c288bb2c76cbddacb1dae07032ec471c7ff8b49cb3da3ca4ba99de2d60419a
Both payments are on their chains and locked to the same secret hash 6caa573398b376b9bf092df0c8820b004faa7502, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 10c288bb2c76cbddacb1dae07032ec471c7ff8b49cb3da3ca4ba99de2d60419a
- MakerPaymentSpent: 6bb6bbf543838089a136c1a097c4f868c1fa76c252887f8f7d46767b0b69391d
c5eed8eee7d63e8da45487c41cd865dc220a647009002cb031e8387afaed2ef3
Both payments are on their chains and locked to the same secret hash 6caa573398b376b9bf092df0c8820b004faa7502, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5188e1a79f4997e5ff17d3c7a30c2ab34ad5fc7fcb5c7004ea4676cf5251f659
- TakerPaymentSent · TakerPaymentReceived: c5eed8eee7d63e8da45487c41cd865dc220a647009002cb031e8387afaed2ef3
- TakerPaymentSpent: f39986da69dea15421b97c1f7c42fa0b878bff97dca7f29a45813a4973954de1
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.