Transaction Details
Tx hash
30ba7a9ae57124cec2a7fec05b7dde2f6c5e98bd58b3db884249c3e5a83e659d
Tx prefix hash
86cf7e9e0a8a61813286a1a5feab1a810cc24571e5d092c3324eefe25c8a8b89
Tx public key
1f36e8f990ff815e90094d1ca5c74fb8586d0d1899b88f7a759fb7a1758598b9
Age [y:d:h:m:s]
05:264:14:55:04
Timestamp [UCT] (epoch)
2019-03-08 19:57:06 (1552075026)
Block
128717 (1470395 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011f36e8f990ff815e90094d1ca5c74fb8586d0d1899b88f7a759fb7a1758598b903210036f80cff0b385c46de98a6b3f48d88ed2d4e5e8db9358ed6717de561eceeb26e021b0000000000000000000000000025979eb800000000000000000000
Outputs
1 output(s) for total of 19.059190253 ARQ
stealth address amount amount idx
00: 1b7f4cefe8578bbd68aa356d4a23f2ebe7f6004d5466b1fd39994ffef2d8f1fb 19.059190253 613627 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": 128735, 
  "vin": [ {
      "gen": {
        "height": 128717
      }
    }
  ], 
  "vout": [ {
      "amount": 19059190253, 
      "target": {
        "key": "1b7f4cefe8578bbd68aa356d4a23f2ebe7f6004d5466b1fd39994ffef2d8f1fb"
      }
    }
  ], 
  "extra": [ 1, 31, 54, 232, 249, 144, 255, 129, 94, 144, 9, 77, 28, 165, 199, 79, 184, 88, 109, 13, 24, 153, 184, 143, 122, 117, 159, 183, 161, 117, 133, 152, 185, 3, 33, 0, 54, 248, 12, 255, 11, 56, 92, 70, 222, 152, 166, 179, 244, 141, 136, 237, 45, 78, 94, 141, 185, 53, 142, 214, 113, 125, 229, 97, 236, 238, 178, 110, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 37, 151, 158, 184, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}