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.
52b44dbf98d2e3cfba7b2718883b2341e244ed3aa3de6b516515cf4e80502b5a
Both payments are on their chains and locked to the same secret hash 48fe2e1575341a3651e4046fc0e6bbf2d9b5127f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 52b44dbf98d2e3cfba7b2718883b2341e244ed3aa3de6b516515cf4e80502b5a
- MakerPaymentSpent: 35388f8f544e3f2cc7cbc37d81d1489f4ec470b0f0d78620bffa771af347fdc8
eca45a5db6215c336b516b695e5cc65519359c5341b19e71bee6f84f9cf9fb26
Both payments are on their chains and locked to the same secret hash 48fe2e1575341a3651e4046fc0e6bbf2d9b5127f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d77b67e15723466c8e0a549705395f1d43e7dd9695bbe56b85cc34d9e5b43a85
- TakerPaymentSent · TakerPaymentReceived: eca45a5db6215c336b516b695e5cc65519359c5341b19e71bee6f84f9cf9fb26
- TakerPaymentSpent: f72a4feac0dbdc2f7dfa6d1942d466048477b910b5e7ac0dc467e4ddf3ec3bf3
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.