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.
a595cc65754d15741e7a56588d98a97512665cadf96b471dfafda6b9e5ba7629
Both payments are on their chains and locked to the same secret hash 1bc69d56f4896c5743e3e2ed7dd85e37f3c3a4c7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a595cc65754d15741e7a56588d98a97512665cadf96b471dfafda6b9e5ba7629
- MakerPaymentSpent: 677aecac15aece5f1b4f58d65eea6538c4c76e0f5ebcb7e8941fad8bde0ea414
9ec1c7ac30ead84c56cea1b7683f67b45c7a393f23437ceced9f01d5503f678b
Both payments are on their chains and locked to the same secret hash 1bc69d56f4896c5743e3e2ed7dd85e37f3c3a4c7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 61ddee77e67440263c06effdb65eccbb1c3f42e0b0f097cc82956fdde1a472f1
- TakerPaymentSent · TakerPaymentReceived: 9ec1c7ac30ead84c56cea1b7683f67b45c7a393f23437ceced9f01d5503f678b
- TakerPaymentSpent: 6e04dbff59704db1051dd6e4c884e8c3eaa0e50e3e23d6afba9a5024147775d6
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.