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.
badc3205b46730003298cc5b4f2f76032e31eb01cf1ed2a4720371f3c1738b1f
Both payments are on their chains and locked to the same secret hash c9f2562a4af3b454499861a2982794c966d3ad66, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: badc3205b46730003298cc5b4f2f76032e31eb01cf1ed2a4720371f3c1738b1f
- MakerPaymentSpent: d2d5258721e5f40769f900d8a641b20904d48f9e5515ac7f522981e52d2c6a86
9e0decdb04dba52529ac8d3bd3641f90fa9aca2c0c78090acc5732f0fe342305
Both payments are on their chains and locked to the same secret hash c9f2562a4af3b454499861a2982794c966d3ad66, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2ff3090ff11f72c8ad6958963517780b3cfa91035b4325ae113399d81656a854
- TakerPaymentSent · TakerPaymentReceived: 9e0decdb04dba52529ac8d3bd3641f90fa9aca2c0c78090acc5732f0fe342305
- TakerPaymentSpent: d70922ed624ed2e53ed204a39d8e3066814156d38389d9e7d05e76697cf4246e
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.