Transaction Details
Tx hash
97179988fdc953c3a5b795ed8c0f2e0257bcdf2123ce5be51c1b019b3ed187be
Tx prefix hash
fa6dc86a6c9dc0f91e7435b0d0954d2460d5cd467b6e26064bd921ca9d7234c6
Tx public key
54b2d329f73a8fb04d9003b6edc1464bf8f35f3f0e3dac62399beb39934f95c8
Age [y:d:h:m:s]
05:190:05:30:33
Timestamp [UCT] (epoch)
2019-05-26 21:38:55 (1558906735)
Block
185194 (1417196 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0154b2d329f73a8fb04d9003b6edc1464bf8f35f3f0e3dac62399beb39934f95c8021100000004e43e97870000000000000000000321008888d8be5790f7a728a9a3f7a92a5a186061e09223530b8f1ce51857a710fd96
Outputs
1 output(s) for total of 18.552769454 ARQ
stealth address amount amount idx
00: deb419bd852d81200a798c5e1744061138e0aa9b3f9ecf12b54a7085792d4bfc 18.552769454 833006 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": 185212, 
  "vin": [ {
      "gen": {
        "height": 185194
      }
    }
  ], 
  "vout": [ {
      "amount": 18552769454, 
      "target": {
        "key": "deb419bd852d81200a798c5e1744061138e0aa9b3f9ecf12b54a7085792d4bfc"
      }
    }
  ], 
  "extra": [ 1, 84, 178, 211, 41, 247, 58, 143, 176, 77, 144, 3, 182, 237, 193, 70, 75, 248, 243, 95, 63, 14, 61, 172, 98, 57, 155, 235, 57, 147, 79, 149, 200, 2, 17, 0, 0, 0, 4, 228, 62, 151, 135, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 136, 136, 216, 190, 87, 144, 247, 167, 40, 169, 163, 247, 169, 42, 90, 24, 96, 97, 224, 146, 35, 83, 11, 143, 28, 229, 24, 87, 167, 16, 253, 150
  ], 
  "rct_signatures": {
    "type": 0
  }
}