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.
fbae337dcdf8a3c0f72f24ef0d9a9d6959050fb0ddcfffd539459737143ca0de
Both payments are on their chains and locked to the same secret hash e4731e6bb82b4dd8c2c3741ce4dcf4260ff895ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fbae337dcdf8a3c0f72f24ef0d9a9d6959050fb0ddcfffd539459737143ca0de
- MakerPaymentSpent: 553d6ebb977667a3bd5291deedca011dd27b89f0fc6977e815e8c6d06da85c11
4353dbabdef0856e15a40306d89bfc32629916df2b3632b54079eb97d6333ddb
Both payments are on their chains and locked to the same secret hash e4731e6bb82b4dd8c2c3741ce4dcf4260ff895ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ae9980443f59b085dd51039c12722157e70cc30f779ad45cb82360b8c45a0119
- TakerPaymentSent · TakerPaymentReceived: 4353dbabdef0856e15a40306d89bfc32629916df2b3632b54079eb97d6333ddb
- TakerPaymentSpent: b818a7391c0bc5816d7ece4fffe0a5d6cc9a3081364b2ba5bbd2e42affc43133
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.