Transaction Details
Tx hash
355ffd9d52bc93574830093695e3371a93ad5e2ef24df49b4535f7e7d255548c
Tx prefix hash
f43d20ee3a265ac263012bdb436a69d72c33941d3ae7cdc51379b1323a223ad9
Tx public key
c89f22ec42d0b103a25d63fe261a168be692c28daaadac708d749a48fc4411da
Age [y:d:h:m:s]
05:245:04:35:18
Timestamp [UCT] (epoch)
2019-03-20 00:46:10 (1553042770)
Block
136695 (1456563 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c89f22ec42d0b103a25d63fe261a168be692c28daaadac708d749a48fc4411da032100d94726bfa7b21df1e51e27fcc6a868f9fe51e5fe106e16dcd5c5c570490b0bfd021b00000000000000000000000000517eb18e00000000000000000000
Outputs
1 output(s) for total of 18.986822871 ARQ
stealth address amount amount idx
00: 702d8080b2e03473e62c812d526e0ebda6131d0f49a0e9bc9bb98e846d308517 18.986822871 638660 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": 136713, 
  "vin": [ {
      "gen": {
        "height": 136695
      }
    }
  ], 
  "vout": [ {
      "amount": 18986822871, 
      "target": {
        "key": "702d8080b2e03473e62c812d526e0ebda6131d0f49a0e9bc9bb98e846d308517"
      }
    }
  ], 
  "extra": [ 1, 200, 159, 34, 236, 66, 208, 177, 3, 162, 93, 99, 254, 38, 26, 22, 139, 230, 146, 194, 141, 170, 173, 172, 112, 141, 116, 154, 72, 252, 68, 17, 218, 3, 33, 0, 217, 71, 38, 191, 167, 178, 29, 241, 229, 30, 39, 252, 198, 168, 104, 249, 254, 81, 229, 254, 16, 110, 22, 220, 213, 197, 197, 112, 73, 11, 11, 253, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 81, 126, 177, 142, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}