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.
6d74811a42f262fe4f46088fdb755625b972d423799fd9678b9c7e577e94f3b5
Both payments are on their chains and locked to the same secret hash 8bde01180cc4c6eeb094064c37404f0634b9790b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6d74811a42f262fe4f46088fdb755625b972d423799fd9678b9c7e577e94f3b5
- MakerPaymentSpent: 2f81703208784d45ae8a7f0533a3cebe1337e85d09d31974e718deb259570d98
e35c832a7b2db2e2b45e43ed65da1a50301719005711989030bde678c116ff6a
Both payments are on their chains and locked to the same secret hash 8bde01180cc4c6eeb094064c37404f0634b9790b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2a3f833453597415b95f538a411395674d7c46bf34d21cbbd076b4bdc75d8acd
- TakerPaymentSent · TakerPaymentReceived: e35c832a7b2db2e2b45e43ed65da1a50301719005711989030bde678c116ff6a
- TakerPaymentSpent: 4dd76f91946ef1eb85be2ab91d96a3d85b2cf8ce64849dda422f72c61ebbf49f
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.