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.
5259fcf4c0a6363058276f6bde8afd9a91a005f6556481cebfe7fa1485d9a6c6
Both payments are on their chains and locked to the same secret hash 79c37d86697b829cec3570723272079c6154b607, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5259fcf4c0a6363058276f6bde8afd9a91a005f6556481cebfe7fa1485d9a6c6
- MakerPaymentSpent: e69dfb703005d716cb74eeb6351c208e6b3f536b27e019be3d4e3fb73927d245
3ca67d4cce7b38cc7ff943aa8aac9a00bacd13332d86c58a846755264fbbcfc7
Both payments are on their chains and locked to the same secret hash 79c37d86697b829cec3570723272079c6154b607, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3b526a0cf41bb9d5451aa3847e6168349b1120b0963901448abcab6d23028057
- TakerPaymentSent · TakerPaymentReceived: 3ca67d4cce7b38cc7ff943aa8aac9a00bacd13332d86c58a846755264fbbcfc7
- TakerPaymentSpent: 217fdc916a7eb1c794ee6ec083de2f59be382e7f85ceaa8301d8cf64e18a8c6e
Reported by kdf-statsdb.