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.
a76dee11cedcf73d48a321168b91736642ff5d607ea902c905f12ebf37de253f
Both payments are on their chains and locked to the same secret hash e883ee7379181c52f0b6eb200d85782d744df2cc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a76dee11cedcf73d48a321168b91736642ff5d607ea902c905f12ebf37de253f
- MakerPaymentSpent: b9b24aacb3968f7c3d3fc8f805e7b540f26fa1595eb1ff9a3c0dd1b7962e1294
0f5377afcda60268a1ea81a05d785dedb49863458978b3216d25bc13663432f1
Both payments are on their chains and locked to the same secret hash e883ee7379181c52f0b6eb200d85782d744df2cc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 208bbca9d775ed08059b411df296905fa332fc5c80d3e9839949efc0b35133d1
- TakerPaymentSent · TakerPaymentReceived: 0f5377afcda60268a1ea81a05d785dedb49863458978b3216d25bc13663432f1
- TakerPaymentSpent: ebf55e110ee2a9d6307c5bd01cf8f3ba8534e5c89e943534e0a787506b6d7d2c
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.