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.
391c872181519d455b75cfcd3fc9f48198094a418ad5db67f72d7f5e9cc7e743
Both payments are on their chains and locked to the same secret hash dd8039a9f39a11706eb816526dd38714a11f867b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 391c872181519d455b75cfcd3fc9f48198094a418ad5db67f72d7f5e9cc7e743
- MakerPaymentSpent: 43ebffb8b2b30e1035634f4bbfb756133c2ced13f6b056fa330eb378a407dbdb
a111136b3a35817f71edcb9ee84dc398c72b81bbb04ae4f7feeb43e17a997496
Both payments are on their chains and locked to the same secret hash dd8039a9f39a11706eb816526dd38714a11f867b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1075c129210ccb1dab748f25499f6de9521771b1bb23798ad7294ba84dec4b8c
- TakerPaymentSent · TakerPaymentReceived: a111136b3a35817f71edcb9ee84dc398c72b81bbb04ae4f7feeb43e17a997496
- TakerPaymentSpent: 045ea80f69c2c6e2cfc82c39d4d9a65e2db2cf7972c7e903b5120a668531d757
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.