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.
3018114fec43bb779ea9907f0224a48f4d4516c97b654a1a4c6d1086ea0f6821
Both payments are on their chains and locked to the same secret hash c81be98b9eb4f58b7991e5dc4f4d0870c4dfcc81, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 3018114fec43bb779ea9907f0224a48f4d4516c97b654a1a4c6d1086ea0f6821
- MakerPaymentSpent: 40af7d5d32c3c5cc663b667ae2852b68fe931ce6062c6a0feefca816853d8940
0c04781c2c8d3da9179182541c6cb337661e05eb309fcd1a230cb02446cec344
Both payments are on their chains and locked to the same secret hash c81be98b9eb4f58b7991e5dc4f4d0870c4dfcc81, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0e2f7b698404ce4c60c5b3fa6f8c7560ed3a585ae9ca809a9e405c8265b0c48e
- TakerPaymentSent · TakerPaymentReceived: 0c04781c2c8d3da9179182541c6cb337661e05eb309fcd1a230cb02446cec344
- TakerPaymentSpent: e6e732f597eab20f3a8bb2db5c225fdb98d81217e568a2edc28e9a9e22f6e482
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.