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.
481e7b7b33654fd7948bf6fe5fb07124b89dfcb05848fb1190efb94f306f68e8
Both payments are on their chains and locked to the same secret hash 997f8f38dfb53137c3bb6546cfd849aa5b8cbc15, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 481e7b7b33654fd7948bf6fe5fb07124b89dfcb05848fb1190efb94f306f68e8
- MakerPaymentSpent: bcd3ec00c507435707d491b4511d470f796d50b99d7142cc30b86d41521c02d7
a0fd27b5450d0174bd588997c01aa4a781b7a0c6b06730227e5ecc34495b257c
Both payments are on their chains and locked to the same secret hash 997f8f38dfb53137c3bb6546cfd849aa5b8cbc15, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 42ab5539050e8ac21bcc3a4e3d6e278bf43570d08f0572ec6225b778d81419f8
- TakerPaymentSent · TakerPaymentReceived: a0fd27b5450d0174bd588997c01aa4a781b7a0c6b06730227e5ecc34495b257c
- TakerPaymentSpent: 60f5033d93aabcf49eedfa3e2625fcc4251d293da97f5873195c4a9bed08c360
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.