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.
e0ed8a74ce25a206da373177b97ab452f33ce15e87d10d149ac778ddc88d300c
Both payments are on their chains and locked to the same secret hash 1f6dde8fbd79bdfe19562fc0dc42be536362e70a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e0ed8a74ce25a206da373177b97ab452f33ce15e87d10d149ac778ddc88d300c
- MakerPaymentSpent: b062818128b7aa000b4465ccb3b4b6feae97598241382ae54687ae88b198b0e8
cf013b0ae4492ce4e64880887aae7b22068b0e4da89bbbc65a8babb572856d97
Both payments are on their chains and locked to the same secret hash 1f6dde8fbd79bdfe19562fc0dc42be536362e70a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b387f0718433ef307d3de05c534d059a245e45d296817bef0afb9c00602c08d7
- TakerPaymentSent · TakerPaymentReceived: cf013b0ae4492ce4e64880887aae7b22068b0e4da89bbbc65a8babb572856d97
- TakerPaymentSpent: 418880045eecd7813535153bf68fd8ec8e05bed85575d090ff60f8bd7ea8f26c
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.