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.
0e4b4de955209081179eeaeddf2d0615a4e0209c002e6243c6cb1160bdb2d33e
Both payments are on their chains and locked to the same secret hash 9124994aa0aa8686094e50d3222c73eab33bf7ec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0e4b4de955209081179eeaeddf2d0615a4e0209c002e6243c6cb1160bdb2d33e
- MakerPaymentSpent: 7b4a44f81769930e3f8a235c03671a9ab9fd7d508aba1c69fcc8e463dfc9bedb
12bd519d5f53f568cbabbcb45144801347ff9b455a6a7b5d34e56e30bfa9df28
Both payments are on their chains and locked to the same secret hash 9124994aa0aa8686094e50d3222c73eab33bf7ec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d2d831a04c2b4bc69f43d7610b1b27dffdbd469ec1eff743e7c47bc76b682127
- TakerPaymentSent · TakerPaymentReceived: 12bd519d5f53f568cbabbcb45144801347ff9b455a6a7b5d34e56e30bfa9df28
- TakerPaymentSpent: 38b379080b76d4b7d2143f383465ab4ddf76fd55a46b5f7d59e5b8fa89c81d82
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.