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.
8524b8a18e2de9c4b6f4c7b1ed53a9ef8aef6c510690cdeeb96ede1ed72b0631
Both payments are on their chains and locked to the same secret hash 46269c36cf95a9df72f8060617dec5f537a5b83f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8524b8a18e2de9c4b6f4c7b1ed53a9ef8aef6c510690cdeeb96ede1ed72b0631
- MakerPaymentSpent: 05f8ddb476e34aed08b15f7a4c3334490ebf537ca66bbd15b5ef3814d1c1e2ee
5eca69ad9e3a90a44522c5c713d152e366b5cb147a5e73efb8ca88e07643c755
Both payments are on their chains and locked to the same secret hash 46269c36cf95a9df72f8060617dec5f537a5b83f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58d47618fad089f39a9a57db97e55eebddfcc117fc21fa6c51d0fd2f91909616
- TakerPaymentSent · TakerPaymentReceived: 5eca69ad9e3a90a44522c5c713d152e366b5cb147a5e73efb8ca88e07643c755
- TakerPaymentSpent: 8ea5568e41a7abd42634b0368f305c6d0e92208508743920be115caad5262a4d
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.