Transaction Details
Tx hash
155c54b9f12371ee27a7e3ab34f1f0ca1c55bf169202290cbf2832fc2af04bdb
Tx prefix hash
832a5bf0502285387f66264c493f9dbbbba6401bc315259294d96c25f07760e9
Tx public key
3a49da775e93a4a301904a94677cecd6a3e0d8452366f3767ae59be5d940badd
Age [y:d:h:m:s]
05:318:23:33:36
Timestamp [UCT] (epoch)
2019-01-12 03:50:51 (1547265051)
Block
88941 (1509247 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013a49da775e93a4a301904a94677cecd6a3e0d8452366f3767ae59be5d940badd03210072e142dda6af2652f6eb017ee929ff85b706c2f00a439cc6b2a941528e8b28f4021b000000000000000000000000000836d44000000000000000000000
Outputs
1 output(s) for total of 19.424229739 ARQ
stealth address amount amount idx
00: 1fc655957df393007edaddbb0e042e7f7ea3508d154fdc377f511cd68141f764 19.424229739 439849 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": 88959, 
  "vin": [ {
      "gen": {
        "height": 88941
      }
    }
  ], 
  "vout": [ {
      "amount": 19424229739, 
      "target": {
        "key": "1fc655957df393007edaddbb0e042e7f7ea3508d154fdc377f511cd68141f764"
      }
    }
  ], 
  "extra": [ 1, 58, 73, 218, 119, 94, 147, 164, 163, 1, 144, 74, 148, 103, 124, 236, 214, 163, 224, 216, 69, 35, 102, 243, 118, 122, 229, 155, 229, 217, 64, 186, 221, 3, 33, 0, 114, 225, 66, 221, 166, 175, 38, 82, 246, 235, 1, 126, 233, 41, 255, 133, 183, 6, 194, 240, 10, 67, 156, 198, 178, 169, 65, 82, 142, 139, 40, 244, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 8, 54, 212, 64, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}