Transaction Details
Tx hash
c0c7291c4cf84bc1eae757a03edb28687263f753aa5da68c671e7a67f188fa48
Tx prefix hash
1c191dd45d29f2b962600b41f53e1f601ccd0e24fa3a7b36d1e77e5925de470a
Tx public key
b6d8caedacb1f4a2baf96061bdeede8aae2b94349a376785355c4e5f15f6a8a5
Age [y:d:h:m:s]
05:169:03:15:41
Timestamp [UCT] (epoch)
2019-06-11 16:37:05 (1560271025)
Block
196358 (1402317 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01b6d8caedacb1f4a2baf96061bdeede8aae2b94349a376785355c4e5f15f6a8a5032100d4278639ee3c9ff868328f3bee7c7ef190c0418c79b583a25ca22496d856fb0d021b0000000000000000000000000021d2362100000000000000000000
Outputs
1 output(s) for total of 18.454267846 ARQ
stealth address amount amount idx
00: d7203514313fd9b27ba474a05d9d6fc7e520c006e0f1e84d040c6d8811120cb1 18.454267846 887622 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": 196376, 
  "vin": [ {
      "gen": {
        "height": 196358
      }
    }
  ], 
  "vout": [ {
      "amount": 18454267846, 
      "target": {
        "key": "d7203514313fd9b27ba474a05d9d6fc7e520c006e0f1e84d040c6d8811120cb1"
      }
    }
  ], 
  "extra": [ 1, 182, 216, 202, 237, 172, 177, 244, 162, 186, 249, 96, 97, 189, 238, 222, 138, 174, 43, 148, 52, 154, 55, 103, 133, 53, 92, 78, 95, 21, 246, 168, 165, 3, 33, 0, 212, 39, 134, 57, 238, 60, 159, 248, 104, 50, 143, 59, 238, 124, 126, 241, 144, 192, 65, 140, 121, 181, 131, 162, 92, 162, 36, 150, 216, 86, 251, 13, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 33, 210, 54, 33, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}