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.
5fd4530814f56288a11c0245bebaccdef9c61340894e4bb2ee7c073443951367
Both payments are on their chains and locked to the same secret hash 0cb9e53ea7b2170c035652ae6ffdc3c3dd603ff1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5fd4530814f56288a11c0245bebaccdef9c61340894e4bb2ee7c073443951367
- MakerPaymentSpent: 0e4acd8328e8f9efa7f10d187651919a443998b16c08a57d5b03107b0159abb8
0883da49abca4c54d253e6af8f74129aecf6455ddaa377e7cdb5e6a799331ebd
Both payments are on their chains and locked to the same secret hash 0cb9e53ea7b2170c035652ae6ffdc3c3dd603ff1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 46ba607699847957ca85c5670428fbe40fa11628ad99cee15ff25e235f796146
- TakerPaymentSent · TakerPaymentReceived: 0883da49abca4c54d253e6af8f74129aecf6455ddaa377e7cdb5e6a799331ebd
- TakerPaymentSpent: 4b42e43302effa54ecec2e217de72e9b3932f96cc3c7a2483cec6e8dab96b7be
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.