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.
3234b16861e1f02573ed4fd631f871af4fbb9dc03a1843d6cd43f9dbc5ffe8ae
Both payments are on their chains and locked to the same secret hash 2b7dabe7a30b7bdf2d8123e80cb1c2d3c320bb28, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 3234b16861e1f02573ed4fd631f871af4fbb9dc03a1843d6cd43f9dbc5ffe8ae
1848d5d401f014e285fce571da47a9f6e38c38d21b0ddbdb33c6924eb356b3aa
Both payments are on their chains and locked to the same secret hash 2b7dabe7a30b7bdf2d8123e80cb1c2d3c320bb28, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: dcd1bc5d7caa4677a161e23b91978cec7cf552c32157b2da505623e6b1fa74cc
- TakerPaymentReceived: 1848d5d401f014e285fce571da47a9f6e38c38d21b0ddbdb33c6924eb356b3aa
- TakerPaymentSpent: cdd1e4c9698d635d219e92b26e76c2329e45710037ed8935fbf0d6878ab3f9e9
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.