Transaction Details
Tx hash
68e7504a5cf22bde8d699d1c1da2a635539914ee97574404aed9585b4358fc20
Tx prefix hash
7c9e0571ab853ff783f4f57d2ce304024ce2be08138fcfe8a8c093b2ac5da938
Tx public key
a19f78e6cbfa588f76b80f9bf02752634576d669e893a6584646095f26c01c0b
Age [y:d:h:m:s]
05:329:07:23:22
Timestamp [UCT] (epoch)
2019-01-04 23:16:05 (1546643765)
Block
83823 (1516580 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a19f78e6cbfa588f76b80f9bf02752634576d669e893a6584646095f26c01c0b0321007a6da1ba0c14294f80ab21b095e54691027301bae90a7bbcd3a936baa717bfc8021b000000000000000000000000004cfc4c9600000000000000000000
Outputs
1 output(s) for total of 19.471621455 ARQ
stealth address amount amount idx
00: 05a1166a03867ec6bbb94d9efd18e436a6915a09a3c5e6ecf7b69b4b8194a665 19.471621455 415529 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": 83841, 
  "vin": [ {
      "gen": {
        "height": 83823
      }
    }
  ], 
  "vout": [ {
      "amount": 19471621455, 
      "target": {
        "key": "05a1166a03867ec6bbb94d9efd18e436a6915a09a3c5e6ecf7b69b4b8194a665"
      }
    }
  ], 
  "extra": [ 1, 161, 159, 120, 230, 203, 250, 88, 143, 118, 184, 15, 155, 240, 39, 82, 99, 69, 118, 214, 105, 232, 147, 166, 88, 70, 70, 9, 95, 38, 192, 28, 11, 3, 33, 0, 122, 109, 161, 186, 12, 20, 41, 79, 128, 171, 33, 176, 149, 229, 70, 145, 2, 115, 1, 186, 233, 10, 123, 188, 211, 169, 54, 186, 167, 23, 191, 200, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 76, 252, 76, 150, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}