Transaction Details
Tx hash
8b0cfcf3267007a2208a2bfe9d370bf3465e71f29a10d634ea04370dad0fc7b2
Tx prefix hash
06d804dcad6cbd48215dcc449759a5a9c49396cc2470a0f51c7093453e319760
Tx public key
fa92e1374c8e273571df3bc388e9649f7918bfa4f85f764b8494205beca8b061
Age [y:d:h:m:s]
05:306:23:34:51
Timestamp [UCT] (epoch)
2019-01-24 19:01:36 (1548356496)
Block
97936 (1500694 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01fa92e1374c8e273571df3bc388e9649f7918bfa4f85f764b8494205beca8b0610321005754fba7ac49592210a6155deea6a4f417cf43f988915a78c80e64e6b91ca339021b00000000000000000000000000319d03d600000000000000000000
Outputs
1 output(s) for total of 19.341040558 ARQ
stealth address amount amount idx
00: a88339c6a9e0902e8e3bf334512f6fb12685a63c55be7c82cdc4700d07fabc61 19.341040558 483437 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": 97954, 
  "vin": [ {
      "gen": {
        "height": 97936
      }
    }
  ], 
  "vout": [ {
      "amount": 19341040558, 
      "target": {
        "key": "a88339c6a9e0902e8e3bf334512f6fb12685a63c55be7c82cdc4700d07fabc61"
      }
    }
  ], 
  "extra": [ 1, 250, 146, 225, 55, 76, 142, 39, 53, 113, 223, 59, 195, 136, 233, 100, 159, 121, 24, 191, 164, 248, 95, 118, 75, 132, 148, 32, 91, 236, 168, 176, 97, 3, 33, 0, 87, 84, 251, 167, 172, 73, 89, 34, 16, 166, 21, 93, 238, 166, 164, 244, 23, 207, 67, 249, 136, 145, 90, 120, 200, 14, 100, 230, 185, 28, 163, 57, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 49, 157, 3, 214, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}