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.
c6b5d496019b56f4c02ff315602f7ff3995a88c3aa6a593aadc8731d385aeb64
Both payments are on their chains and locked to the same secret hash 189103d9c42b240ee03b3dfeaa4cd21f2e4d44c5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c6b5d496019b56f4c02ff315602f7ff3995a88c3aa6a593aadc8731d385aeb64
- MakerPaymentSpent: a10d7654caf2016d04eaf7bf77d441cc69b8a185d0e6ac426a130a3c505adaff
93a0fd2fbadb660849556063187154c4083e3865b3d33f868a2cbd827a39f90c
Both payments are on their chains and locked to the same secret hash 189103d9c42b240ee03b3dfeaa4cd21f2e4d44c5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5989804adc5b89decc90288053988aa3fad23209d34bd36075e0e6d449ad687a
- TakerPaymentSent · TakerPaymentReceived: 93a0fd2fbadb660849556063187154c4083e3865b3d33f868a2cbd827a39f90c
- TakerPaymentSpent: 73b368b0f84bd8346600ae0f9a047375b9e057a29960c65348428bb403495111
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.