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.
9159a3053445a181ff5a466b684c7a39359b80daa9175e5ac5ab9dee378e50f7
Both payments are on their chains and locked to the same secret hash 501bc2aa306d86863549e8666a16e2edbb5492db, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9159a3053445a181ff5a466b684c7a39359b80daa9175e5ac5ab9dee378e50f7
- MakerPaymentSpent: 58f0229eb5c1877bbd299615ff426e91afaed03d95e4dde6511834bea0fced3b
a16833991d1d16bd9828b1e9a1b516067f1a7f1123ebf5be04e81fae9ef07626
Both payments are on their chains and locked to the same secret hash 501bc2aa306d86863549e8666a16e2edbb5492db, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3c8cf74439c8077f733cd398e71bd6dce7d665e4bf95973ffbc1f54e92bb330f
- TakerPaymentSent · TakerPaymentReceived: a16833991d1d16bd9828b1e9a1b516067f1a7f1123ebf5be04e81fae9ef07626
- TakerPaymentSpent: 4d6cd861188421fd5edf5beb2e5fd56bd25d5fecf7f646df2cd0e5555534124d
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.