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.
99effd44198787aa0ff10f78996af1a91f542abc0eca745e2ce39d2da95392c3
Both payments are on their chains and locked to the same secret hash e20b47c322167d594318a046196e18beedc613cf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 99effd44198787aa0ff10f78996af1a91f542abc0eca745e2ce39d2da95392c3
- MakerPaymentSpent: f748ad7a9e631d4b9b9f21a28247dd29161d89519fe261cbdd073c62f8245237
a5af9e923408d1c17e3926ce809abb9b35687d009b3c29a9c47d22329a85ed78
Both payments are on their chains and locked to the same secret hash e20b47c322167d594318a046196e18beedc613cf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 535bf318cceb051d8ecbcc60fc95386611dd80a5b4e5abc86f787dd17ba10edf
- TakerPaymentSent · TakerPaymentReceived: a5af9e923408d1c17e3926ce809abb9b35687d009b3c29a9c47d22329a85ed78
- TakerPaymentSpent: 604b43ec79aa54b6c33c2dac6fa98f3102a675305efcbfc5e50f417c6e4758b3
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.