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.
5db7fa75681698b6d1759f58104aacd8b8e97ee10746dc0350ca388415d43a5a
Both payments are on their chains and locked to the same secret hash b29602344b66b0fdf5bdd5e461f7befc741f5755, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5db7fa75681698b6d1759f58104aacd8b8e97ee10746dc0350ca388415d43a5a
- MakerPaymentSpent: 274f339606355c2ba73e89af4448f3153ab7fad2253a758a6fabbe08cc29f0ec
5f72707485a04711aaa993ab3baad5587cbe20ef5ac5d45a5f2b76034e500a69
Both payments are on their chains and locked to the same secret hash b29602344b66b0fdf5bdd5e461f7befc741f5755, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4e7a5c41084ef0349c053004a86653417e74240f9ded0dd1135d620bac6dd616
- TakerPaymentSent · TakerPaymentReceived: 5f72707485a04711aaa993ab3baad5587cbe20ef5ac5d45a5f2b76034e500a69
- TakerPaymentSpent: 7d6dc22700599ddc8b0e8f550ddb926322e4eb17988a53c3f016950442acb6f0
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.