Transaction Details
Tx hash
041ee439d5f918f39a88bfb8ec4a95521f6a558433434e0e79bc51227cf6a835
Tx prefix hash
f2918e1d5e77e1a831a2fe079fcbea19e6903442e55af953e5df918e8d7a1e89
Tx public key
d77c841439cbe301f48b3f9fb271b4c2372c2f4f832e0e27b928e39c6d49f84c
Age [y:d:h:m:s]
05:322:20:22:24
Timestamp [UCT] (epoch)
2019-01-11 22:29:03 (1547245743)
Block
88770 (1511985 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01d77c841439cbe301f48b3f9fb271b4c2372c2f4f832e0e27b928e39c6d49f84c03210037d4ac6b9910a5cc6a3a0f2ae3b8a736419c26f276a0cc153e3222fa06cac37f021000000014d41302000000000000000000
Outputs
1 output(s) for total of 19.425712621 ARQ
stealth address amount amount idx
00: d035c0d4b13f80c98da2e46e13528e100c1e70945a4475484f137d51583e0f67 19.425712621 438956 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 88788, 
  "vin": [ {
      "gen": {
        "height": 88770
      }
    }
  ], 
  "vout": [ {
      "amount": 19425712621, 
      "target": {
        "key": "d035c0d4b13f80c98da2e46e13528e100c1e70945a4475484f137d51583e0f67"
      }
    }
  ], 
  "extra": [ 1, 215, 124, 132, 20, 57, 203, 227, 1, 244, 139, 63, 159, 178, 113, 180, 194, 55, 44, 47, 79, 131, 46, 14, 39, 185, 40, 227, 156, 109, 73, 248, 76, 3, 33, 0, 55, 212, 172, 107, 153, 16, 165, 204, 106, 58, 15, 42, 227, 184, 167, 54, 65, 156, 38, 242, 118, 160, 204, 21, 62, 50, 34, 250, 6, 202, 195, 127, 2, 16, 0, 0, 0, 20, 212, 19, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}