Transaction Details
Tx hash
027a9189f47d95388decd55ed70e5f78bacc10881d6f7db9a612ab76ac40a9f6
Tx prefix hash
4574c4463c10423146b620ab27c2db9b6da515e723a6c5e8372254f777f3138d
Tx public key
c4a6ecf6ad2754f9d25e939c5f965eb59060469a9c6e15c63a7b63b1a14d7a2d
Age [y:d:h:m:s]
05:203:03:36:30
Timestamp [UCT] (epoch)
2019-05-11 09:56:57 (1557568617)
Block
174026 (1426582 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c4a6ecf6ad2754f9d25e939c5f965eb59060469a9c6e15c63a7b63b1a14d7a2d0321007dac8964bb9ce852aa7c704d0058c03c6f3c66ec20c90e7d2341c9f4ef20d115021b000000000000000000000000003501d3b100000000000000000000
Outputs
1 output(s) for total of 18.651832400 ARQ
stealth address amount amount idx
00: 7255fc337f9f44def97dd04e7443aef71ea09bb958efa7258bbdd7e314f4f4c2 18.651832400 787859 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": 174044, 
  "vin": [ {
      "gen": {
        "height": 174026
      }
    }
  ], 
  "vout": [ {
      "amount": 18651832400, 
      "target": {
        "key": "7255fc337f9f44def97dd04e7443aef71ea09bb958efa7258bbdd7e314f4f4c2"
      }
    }
  ], 
  "extra": [ 1, 196, 166, 236, 246, 173, 39, 84, 249, 210, 94, 147, 156, 95, 150, 94, 181, 144, 96, 70, 154, 156, 110, 21, 198, 58, 123, 99, 177, 161, 77, 122, 45, 3, 33, 0, 125, 172, 137, 100, 187, 156, 232, 82, 170, 124, 112, 77, 0, 88, 192, 60, 111, 60, 102, 236, 32, 201, 14, 125, 35, 65, 201, 244, 239, 32, 209, 21, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 53, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}