Transaction Details
Tx hash
bd7d911fdd11951b1a6e67ac99673df0c526319f41b08afc6999296b6dfd0034
Tx prefix hash
0df9ef819c1641448c521f17a5387241b003c309c84533ba03268819e3e85221
Tx public key
9aa0d934ca1cac65eff769ab97a88423b88ac5565a768aece8dc7ed4c8617c30
Age [y:d:h:m:s]
05:329:21:30:03
Timestamp [UCT] (epoch)
2019-01-04 20:00:24 (1546632024)
Block
83732 (1516988 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019aa0d934ca1cac65eff769ab97a88423b88ac5565a768aece8dc7ed4c8617c30032100d8ffd43d431fcd5ed226e39e56a01ceab439a89429b52fdde97b807231c35bee021b000000000000000000000000000b3190d300000000000000000000
Outputs
1 output(s) for total of 19.472435229 ARQ
stealth address amount amount idx
00: a97168a44d33a6753d2fcb6b3e55e97987e94bc8d2a144a7d029526551078a5a 19.472435229 415065 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": 83750, 
  "vin": [ {
      "gen": {
        "height": 83732
      }
    }
  ], 
  "vout": [ {
      "amount": 19472435229, 
      "target": {
        "key": "a97168a44d33a6753d2fcb6b3e55e97987e94bc8d2a144a7d029526551078a5a"
      }
    }
  ], 
  "extra": [ 1, 154, 160, 217, 52, 202, 28, 172, 101, 239, 247, 105, 171, 151, 168, 132, 35, 184, 138, 197, 86, 90, 118, 138, 236, 232, 220, 126, 212, 200, 97, 124, 48, 3, 33, 0, 216, 255, 212, 61, 67, 31, 205, 94, 210, 38, 227, 158, 86, 160, 28, 234, 180, 57, 168, 148, 41, 181, 47, 221, 233, 123, 128, 114, 49, 195, 91, 238, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 49, 144, 211, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}