Transaction Details
Tx hash
66707045b6fbbb757de5071c5161fe1ceafa739dac8f1bba096ebc7a3d424d32
Tx prefix hash
434a53be939fc7a0c089c7ed6ceaa89fa199aaa9a386add1638132a697a0cb7c
Tx public key
4158ff748f1557613905b80aac3955d64b5a90cdecf0391199390bcc0e7d4aea
Age [y:d:h:m:s]
05:328:09:39:03
Timestamp [UCT] (epoch)
2019-01-05 18:09:24 (1546711764)
Block
84407 (1515917 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014158ff748f1557613905b80aac3955d64b5a90cdecf0391199390bcc0e7d4aea032100bbe507a031d88ede65a3edaf2da48520bffacf6ea330b14c71d4dc55b35169a9021b0000000000000000000000000013ec9b6f00000000000000000000
Outputs
1 output(s) for total of 19.466215479 ARQ
stealth address amount amount idx
00: 04948c71a9161c1f72ce1d7eb6491bf8a951058d2a328269927f22a9f93fbccd 19.466215479 418047 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": 84425, 
  "vin": [ {
      "gen": {
        "height": 84407
      }
    }
  ], 
  "vout": [ {
      "amount": 19466215479, 
      "target": {
        "key": "04948c71a9161c1f72ce1d7eb6491bf8a951058d2a328269927f22a9f93fbccd"
      }
    }
  ], 
  "extra": [ 1, 65, 88, 255, 116, 143, 21, 87, 97, 57, 5, 184, 10, 172, 57, 85, 214, 75, 90, 144, 205, 236, 240, 57, 17, 153, 57, 11, 204, 14, 125, 74, 234, 3, 33, 0, 187, 229, 7, 160, 49, 216, 142, 222, 101, 163, 237, 175, 45, 164, 133, 32, 191, 250, 207, 110, 163, 48, 177, 76, 113, 212, 220, 85, 179, 81, 105, 169, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 19, 236, 155, 111, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}