Transaction Details
Tx hash
9bb7f2ff4f6cb0e8c9a2f869c1424cea284def0ce08fc6ca2dd8f44c5cec3329
Tx prefix hash
4e0609abddd4c3ad64f5410c1a580d7df31c04d628d6fffa846712e625ab73fc
Tx public key
8524c7cbcd79e738b9120734a55a2d730d0c5b8054e2ebc6d2c95f106a1b6324
Age [y:d:h:m:s]
05:150:11:33:30
Timestamp [UCT] (epoch)
2019-05-10 20:56:25 (1557521785)
Block
173631 (1389422 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018524c7cbcd79e738b9120734a55a2d730d0c5b8054e2ebc6d2c95f106a1b6324032100acd12abd7eedd782e94ebdfeedb1275ecede003e5e1ae5a76418d64b9bf5e0c4021b00000000000000000000000000a101d3b100000000000000000000
Outputs
1 output(s) for total of 18.655345817 ARQ
stealth address amount amount idx
00: 1961790388e65c8b3501c2ac78a7b2694ea55851e3beb8ef10ef033e6b07f3dc 18.655345817 786544 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": 173649, 
  "vin": [ {
      "gen": {
        "height": 173631
      }
    }
  ], 
  "vout": [ {
      "amount": 18655345817, 
      "target": {
        "key": "1961790388e65c8b3501c2ac78a7b2694ea55851e3beb8ef10ef033e6b07f3dc"
      }
    }
  ], 
  "extra": [ 1, 133, 36, 199, 203, 205, 121, 231, 56, 185, 18, 7, 52, 165, 90, 45, 115, 13, 12, 91, 128, 84, 226, 235, 198, 210, 201, 95, 16, 106, 27, 99, 36, 3, 33, 0, 172, 209, 42, 189, 126, 237, 215, 130, 233, 78, 189, 254, 237, 177, 39, 94, 206, 222, 0, 62, 94, 26, 229, 167, 100, 24, 214, 75, 155, 245, 224, 196, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 161, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}