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.
c7defab5e195458c0fe813b58f9c0dba841b4e05adf72705606798d8919f08f1
Both payments are on their chains and locked to the same secret hash 60e6bf5c3997e278e40e890cd220694c74e00caa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c7defab5e195458c0fe813b58f9c0dba841b4e05adf72705606798d8919f08f1
- MakerPaymentSpent: 387c1fc7a642f0eb0caa952bd573cfb341e375b7727e872d8e929de2264e2aa4
3bab06d9d88e7f409007d7cac9f962007097e65f73b09081f3e20ec5c31cddbc
Both payments are on their chains and locked to the same secret hash 60e6bf5c3997e278e40e890cd220694c74e00caa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8fb7fac92b0ff7fce73b31134b6e1ba1c69697b3ac0a15b4ac9c5f33e2a244bd
- TakerPaymentSent · TakerPaymentReceived: 3bab06d9d88e7f409007d7cac9f962007097e65f73b09081f3e20ec5c31cddbc
- TakerPaymentSpent: 697e74feb33671269a6b696f3383cda40f02c7deb6cd6180a1c9c1d781cef5ed
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.