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.
52b80cf3145e18518a3f5b87d1020080685087ccbbcda1ee7282add1cb0041db
Both payments are on their chains and locked to the same secret hash bcc05d7ece4ca4507e71c59d883da0c6565c0953, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 52b80cf3145e18518a3f5b87d1020080685087ccbbcda1ee7282add1cb0041db
- MakerPaymentSpent: 433e8c5b42ed68bf46aa0f0ae94c425658d137060492bb52974c37480335b4df
28e8db72186faa578522724c619e1ce40b3187455db79ed245c9cbd3bf3d7a92
Both payments are on their chains and locked to the same secret hash bcc05d7ece4ca4507e71c59d883da0c6565c0953, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8fce1482a9bd5a50816653ccc3ad91c3edb84af6e42374ed710a48631234dd27
- TakerPaymentSent · TakerPaymentReceived: 28e8db72186faa578522724c619e1ce40b3187455db79ed245c9cbd3bf3d7a92
- TakerPaymentSpent: 0509e7660f144f938459667e1b0cf5568380c8790d985e3374d8efedcd62301d
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.