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.
362323151959bfc08d605cd01b2f1e1adda3624adcf15e634487a386f382e0c9
Both payments are on their chains and locked to the same secret hash 2758006275a6662a5bb917f5fab2f0399f85bd94, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 362323151959bfc08d605cd01b2f1e1adda3624adcf15e634487a386f382e0c9
- MakerPaymentSpent: 187ea3bbda181578f34b61b7105cbb6eecca2fcb213066af9c39851e53639d54
7ac4137f65fe51d31d5ee2158402c8382449ae48dc5d57ae9feb30b56492041d
Both payments are on their chains and locked to the same secret hash 2758006275a6662a5bb917f5fab2f0399f85bd94, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c2f2020ee998fa3093cc3aff16d17b4ae71d53c50d46d53564373a83d5d1b967
- TakerPaymentSent · TakerPaymentReceived: 7ac4137f65fe51d31d5ee2158402c8382449ae48dc5d57ae9feb30b56492041d
- TakerPaymentSpent: 07fcc93440fa514ab494a03811284463d3cefb961ae4ac4291adf591d31ee058
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.