Transaction Details
Tx hash
f991594e9653f3e8270c81d67c0ec98b45a7f7cd023516441f2e810d9c545c21
Tx prefix hash
267a36dcdcfe542b4f5c109df7f79f69b2dcc9048ad068f105da1943b80a5e16
Tx public key
9d46ce9f9d1f0cb48fa17219a213d250c8334a7f614a33af3f2a03a26d7f6e4a
Age [y:d:h:m:s]
05:067:15:08:06
Timestamp [UCT] (epoch)
2019-09-13 10:58:21 (1568372301)
Block
263157 (1329997 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
019d46ce9f9d1f0cb48fa17219a213d250c8334a7f614a33af3f2a03a26d7f6e4a021100000010e9fcaeee0000000000000000000321005758ce4aabcbbb276c914d814be8e0b49d4f0f030c5b0232239116f03ba67b0c
Outputs
1 output(s) for total of 20.290318510 ARQ
stealth address amount amount idx
00: ee903052885c442ce8c88f5ffc1f2d8969fd4d764b32511cd47318b50dc9f87c 20.290318510 1175585 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": 263175, 
  "vin": [ {
      "gen": {
        "height": 263157
      }
    }
  ], 
  "vout": [ {
      "amount": 20290318510, 
      "target": {
        "key": "ee903052885c442ce8c88f5ffc1f2d8969fd4d764b32511cd47318b50dc9f87c"
      }
    }
  ], 
  "extra": [ 1, 157, 70, 206, 159, 157, 31, 12, 180, 143, 161, 114, 25, 162, 19, 210, 80, 200, 51, 74, 127, 97, 74, 51, 175, 63, 42, 3, 162, 109, 127, 110, 74, 2, 17, 0, 0, 0, 16, 233, 252, 174, 238, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 87, 88, 206, 74, 171, 203, 187, 39, 108, 145, 77, 129, 75, 232, 224, 180, 157, 79, 15, 3, 12, 91, 2, 50, 35, 145, 22, 240, 59, 166, 123, 12
  ], 
  "rct_signatures": {
    "type": 0
  }
}