Transaction Details
Tx hash
2c9dd5155ee0dce63db9a7b2e4c5c28382afef9a7c8274d68d6d802bf31e18c0
Tx prefix hash
2d07c5d9c3edcee61a9659daad1c1da2e56454f71560eec37d999498d04f5210
Tx public key
657dc5d969a1ded15c3c2818cf5d8f84e588ea5a9b3d42aa654cef459abd6e5a
Age [y:d:h:m:s]
05:320:01:01:01
Timestamp [UCT] (epoch)
2019-01-12 01:39:15 (1547257155)
Block
88873 (1509994 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01657dc5d969a1ded15c3c2818cf5d8f84e588ea5a9b3d42aa654cef459abd6e5a0321002af46f649fb186d6060b9dbe6a2ae9bcbe2fd2ab25a5cc86c17200076ebf41e7021b000000000000000000000000002536d44000000000000000000000
Outputs
1 output(s) for total of 19.424758565 ARQ
stealth address amount amount idx
00: 8501f6ea2c68f647048d33b7835aa9cf816dc1dd7fc63c15e5cd59c7dac7956d 19.424758565 439476 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": 88891, 
  "vin": [ {
      "gen": {
        "height": 88873
      }
    }
  ], 
  "vout": [ {
      "amount": 19424758565, 
      "target": {
        "key": "8501f6ea2c68f647048d33b7835aa9cf816dc1dd7fc63c15e5cd59c7dac7956d"
      }
    }
  ], 
  "extra": [ 1, 101, 125, 197, 217, 105, 161, 222, 209, 92, 60, 40, 24, 207, 93, 143, 132, 229, 136, 234, 90, 155, 61, 66, 170, 101, 76, 239, 69, 154, 189, 110, 90, 3, 33, 0, 42, 244, 111, 100, 159, 177, 134, 214, 6, 11, 157, 190, 106, 42, 233, 188, 190, 47, 210, 171, 37, 165, 204, 134, 193, 114, 0, 7, 110, 191, 65, 231, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 37, 54, 212, 64, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}