Transaction Details
Tx hash
470bc31458da71fb3169e1473fdbe34bd7b960324886e6829b8bc7e605261f8a
Tx prefix hash
5794e83a795a868c77ce890f0b255f3b1fc0aba988db3059190e1e18837f29c8
Tx public key
9410d9612e7cea4b8863e928f8dbf213900026a8aa50405393d3da0addc1fcc2
Age [y:d:h:m:s]
05:101:11:20:13
Timestamp [UCT] (epoch)
2019-08-23 14:45:58 (1566571558)
Block
248666 (1353692 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019410d9612e7cea4b8863e928f8dbf213900026a8aa50405393d3da0addc1fcc20321008b006d5024a49a3afd2eb837141f18920915e8603a3aaa27b1f46ce0f1565043021b000000000000000000000000030f49380e00000000000000000000
Outputs
1 output(s) for total of 20.430996219 ARQ
stealth address amount amount idx
00: 64c6eabad29c88443541860e14d5c764eb89e3ad4fe7287ae4c00b5fe1be6551 20.430996219 1111957 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": 248684, 
  "vin": [ {
      "gen": {
        "height": 248666
      }
    }
  ], 
  "vout": [ {
      "amount": 20430996219, 
      "target": {
        "key": "64c6eabad29c88443541860e14d5c764eb89e3ad4fe7287ae4c00b5fe1be6551"
      }
    }
  ], 
  "extra": [ 1, 148, 16, 217, 97, 46, 124, 234, 75, 136, 99, 233, 40, 248, 219, 242, 19, 144, 0, 38, 168, 170, 80, 64, 83, 147, 211, 218, 10, 221, 193, 252, 194, 3, 33, 0, 139, 0, 109, 80, 36, 164, 154, 58, 253, 46, 184, 55, 20, 31, 24, 146, 9, 21, 232, 96, 58, 58, 170, 39, 177, 244, 108, 224, 241, 86, 80, 67, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 15, 73, 56, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}