Transaction Details
Tx hash
6a4a62dc1b7919ed935506f6e2bce3222a433b69a86d6c708f2e5ea362f0158f
Tx prefix hash
5dc014c95b8fa53ed7dbd20345cab5d6366a2d53c9a0449905fa9856899b36c4
Tx public key
9e9b7a73ea70df0c3dfbdf0ad9b9cb51e8eb2d695c83d2d4bebb08bc47dc8ead
Age [y:d:h:m:s]
05:228:02:12:07
Timestamp [UCT] (epoch)
2019-04-16 13:12:20 (1555420340)
Block
156160 (1444506 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019e9b7a73ea70df0c3dfbdf0ad9b9cb51e8eb2d695c83d2d4bebb08bc47dc8ead032100063b507af08af051a22b38ebe4060194972ca5291b7e57569d7b5ff74a92d439021b000000000000000000000000001968aeda00000000000000000000
Outputs
1 output(s) for total of 18.811642815 ARQ
stealth address amount amount idx
00: 5a84385110e333e28ddffcacc94f79b2fff2898f13b9a2d49d2d0047aa580a3e 18.811642815 715546 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": 156178, 
  "vin": [ {
      "gen": {
        "height": 156160
      }
    }
  ], 
  "vout": [ {
      "amount": 18811642815, 
      "target": {
        "key": "5a84385110e333e28ddffcacc94f79b2fff2898f13b9a2d49d2d0047aa580a3e"
      }
    }
  ], 
  "extra": [ 1, 158, 155, 122, 115, 234, 112, 223, 12, 61, 251, 223, 10, 217, 185, 203, 81, 232, 235, 45, 105, 92, 131, 210, 212, 190, 187, 8, 188, 71, 220, 142, 173, 3, 33, 0, 6, 59, 80, 122, 240, 138, 240, 81, 162, 43, 56, 235, 228, 6, 1, 148, 151, 44, 165, 41, 27, 126, 87, 86, 157, 123, 95, 247, 74, 146, 212, 57, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 25, 104, 174, 218, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}