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.
afbb33812b9983b8b6275eec81c99783249bab182f392f5f2f70accb44ad8d81
Both payments are on their chains and locked to the same secret hash 73553a9fa75dd4a01ed4fe15c8910574e039f750, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: afbb33812b9983b8b6275eec81c99783249bab182f392f5f2f70accb44ad8d81
- MakerPaymentSpent: 893c5fd41da948de646ed96091ad9c436ef5317af44ce98db649e2f4c4169c77
d42781396a83ffc16fc31d6d26891879abf44c4d74755b93d4ae185ae9cc2588
Both payments are on their chains and locked to the same secret hash 73553a9fa75dd4a01ed4fe15c8910574e039f750, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1c39723d91b45d5a0259197461fee293323259c055059c59988aecee44fd43ec
- TakerPaymentSent · TakerPaymentReceived: d42781396a83ffc16fc31d6d26891879abf44c4d74755b93d4ae185ae9cc2588
- TakerPaymentSpent: 82e18e642fa437e579ddc00e0382b7c5e9f2ce3f3ef092859c6d4b3d5868f35b
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.