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.
5f6ee1fcc4e3f543638265ceed2c00ccf45550d6bb4d6598251c88a9a68c0e78
Both payments are on their chains and locked to the same secret hash d495a45fbaabd0c736e964aaa30b4ee331ccf764, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5f6ee1fcc4e3f543638265ceed2c00ccf45550d6bb4d6598251c88a9a68c0e78
- MakerPaymentSpent: a6490302c194baad61086715e6323643ce17e365b802ada795439f5a3fb009bb
547e576aa303381518d467c851fcb1a4d1560db5a47ee5e5707f29c9408ae444
Both payments are on their chains and locked to the same secret hash d495a45fbaabd0c736e964aaa30b4ee331ccf764, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 61795bb2201bc39297115512436d46d99722eecca3f36cee538cfea84f792a26
- TakerPaymentSent · TakerPaymentReceived: 547e576aa303381518d467c851fcb1a4d1560db5a47ee5e5707f29c9408ae444
- TakerPaymentSpent: 4dbb497daf6df4b91b1f45875dc8671dc5f6443b4106e0b2a3d50793367d91ce
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.