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.
5ac209ed5bbab9e34ca2b15180f149d8e1fbf2f998697747199a2fe56195b4db
Both payments are on their chains and locked to the same secret hash 9a20d638fe40095b2734b4c46b1e386e14647618, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5ac209ed5bbab9e34ca2b15180f149d8e1fbf2f998697747199a2fe56195b4db
- MakerPaymentSpent: 874cef6aa0e8b905cf23f526f50a0b60b0c264ce492cb5bc48f3291b86132be6
b5d663d3faea34bc91621462b1889b80f33a49a35386a42ad107074d82753aec
Both payments are on their chains and locked to the same secret hash 9a20d638fe40095b2734b4c46b1e386e14647618, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1cc3a91b05d30a13649fb916b8a8e7df87a59d1342147d8e2be1599132bf71c7
- TakerPaymentSent · TakerPaymentReceived: b5d663d3faea34bc91621462b1889b80f33a49a35386a42ad107074d82753aec
- TakerPaymentSpent: e621f57875996231f1268037890c97370cc99a313d4c7d2847404095cbab6938
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.