Transaction Details
Tx hash
4f65d134af29a346268fd0f5b9629490c148edbbe1385ec72f26c4f1dfd94739
Tx prefix hash
e1ff30aac109d655ae0edab020230c7ef30272dac0cfe04f6c4220fa3f2389e4
Tx public key
2197bcc059c135937d2c0058af7acde458a1fdf8ab6b508cc0bce9f99c1dd862
Age [y:d:h:m:s]
05:328:18:58:56
Timestamp [UCT] (epoch)
2019-01-06 12:28:31 (1546777711)
Block
84933 (1516181 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
012197bcc059c135937d2c0058af7acde458a1fdf8ab6b508cc0bce9f99c1dd862032100cf4389aa9fc5eae21fb4fa8cd38570f0a857b5a3784044351a7e3525976b205e021b000000000000000000000000000b41474100000000000000000000
Outputs
1 output(s) for total of 19.461286916 ARQ
stealth address amount amount idx
00: cc0f8227cde0b4e4f93a08db7f083a093f4c4ac2e87f8d0e4ee00f84d5c1cb2f 19.461286916 420405 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": 84951, 
  "vin": [ {
      "gen": {
        "height": 84933
      }
    }
  ], 
  "vout": [ {
      "amount": 19461286916, 
      "target": {
        "key": "cc0f8227cde0b4e4f93a08db7f083a093f4c4ac2e87f8d0e4ee00f84d5c1cb2f"
      }
    }
  ], 
  "extra": [ 1, 33, 151, 188, 192, 89, 193, 53, 147, 125, 44, 0, 88, 175, 122, 205, 228, 88, 161, 253, 248, 171, 107, 80, 140, 192, 188, 233, 249, 156, 29, 216, 98, 3, 33, 0, 207, 67, 137, 170, 159, 197, 234, 226, 31, 180, 250, 140, 211, 133, 112, 240, 168, 87, 181, 163, 120, 64, 68, 53, 26, 126, 53, 37, 151, 107, 32, 94, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 65, 71, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}