Transaction Details
Tx hash
c0cac39a0db6e9706c77495061ec8cc0e78b30ccc027f66ce0be3f2b7331baf9
Tx prefix hash
c78fffa6e3cf69ba2d1d036982363a19d8c48c73b711b49d9e9b8d1c1a74bbe7
Tx public key
a67b40dc01f1f61f28bd0859b3ae4f2cfbe723d4c8e6bca2f5f5b60efe5e0059
Age [y:d:h:m:s]
05:223:17:56:17
Timestamp [UCT] (epoch)
2019-04-15 09:07:36 (1555319256)
Block
155345 (1441397 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01a67b40dc01f1f61f28bd0859b3ae4f2cfbe723d4c8e6bca2f5f5b60efe5e0059032100f13101d93af9dfd71677fbe9f13a9240d47ad6cb7e3fb79471b48a696c4b50900210000000062e2201000000000000000000
Outputs
1 output(s) for total of 18.818721341 ARQ
stealth address amount amount idx
00: 9ca8d17b5d26721d6a28302c9f03b24ad520044479d77613a17e77f026e501b5 18.818721341 711384 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": 155363, 
  "vin": [ {
      "gen": {
        "height": 155345
      }
    }
  ], 
  "vout": [ {
      "amount": 18818721341, 
      "target": {
        "key": "9ca8d17b5d26721d6a28302c9f03b24ad520044479d77613a17e77f026e501b5"
      }
    }
  ], 
  "extra": [ 1, 166, 123, 64, 220, 1, 241, 246, 31, 40, 189, 8, 89, 179, 174, 79, 44, 251, 231, 35, 212, 200, 230, 188, 162, 245, 245, 182, 14, 254, 94, 0, 89, 3, 33, 0, 241, 49, 1, 217, 58, 249, 223, 215, 22, 119, 251, 233, 241, 58, 146, 64, 212, 122, 214, 203, 126, 63, 183, 148, 113, 180, 138, 105, 108, 75, 80, 144, 2, 16, 0, 0, 0, 6, 46, 34, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}