Transaction Details
Tx hash
7587fdb9aa71af55f51a0356347b5592a8a100ecf11dc8d619017fa1cf713a56
Tx prefix hash
8d42af2b74188c66771d7138fdd4fec05392b69edfce855b15066582ca32e55b
Tx public key
4448df0359c5ea028f2643459bb5d2d5569af8f95f8fd335af8c0785d8f83830
Age [y:d:h:m:s]
05:018:07:43:16
Timestamp [UCT] (epoch)
2019-11-08 01:38:12 (1573177092)
Block
302764 (1294869 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014448df0359c5ea028f2643459bb5d2d5569af8f95f8fd335af8c0785d8f838300321006f71f1fc774cc447ff23e8191005ef86b7d2bc0dcbf9b95458d2ae268eff6969021b0000000000000000000000000016ee2e6900000000000000000000
Outputs
1 output(s) for total of 19.910704420 ARQ
stealth address amount amount idx
00: 660b34016f5c32138fcd17a859d20eb91843aad43dba84e01aabc12f39df182a 19.910704420 1369173 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": 302782, 
  "vin": [ {
      "gen": {
        "height": 302764
      }
    }
  ], 
  "vout": [ {
      "amount": 19910704420, 
      "target": {
        "key": "660b34016f5c32138fcd17a859d20eb91843aad43dba84e01aabc12f39df182a"
      }
    }
  ], 
  "extra": [ 1, 68, 72, 223, 3, 89, 197, 234, 2, 143, 38, 67, 69, 155, 181, 210, 213, 86, 154, 248, 249, 95, 143, 211, 53, 175, 140, 7, 133, 216, 248, 56, 48, 3, 33, 0, 111, 113, 241, 252, 119, 76, 196, 71, 255, 35, 232, 25, 16, 5, 239, 134, 183, 210, 188, 13, 203, 249, 185, 84, 88, 210, 174, 38, 142, 255, 105, 105, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 22, 238, 46, 105, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}