Transaction Details
Tx hash
55c4b9b146f1e9eeed9f29d1fd44133c4467b744fe2238661167abf61ae1ed26
Tx prefix hash
07b2af3f2035eeace81d2cb272578100689735015f56358245e7b07e5be553fe
Tx public key
2e69c40edb4ed880c4136d6896d942feab779ac9b8bb9dce1db76f8bcee5dba6
Age [y:d:h:m:s]
05:270:01:24:26
Timestamp [UCT] (epoch)
2019-01-10 23:45:02 (1547163902)
Block
88087 (1474746 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
012e69c40edb4ed880c4136d6896d942feab779ac9b8bb9dce1db76f8bcee5dba6032100d055b1ba14cdde16e535e7dd50718f9ef554ac52f466a33c94e83c5ff92fc35e021b000000000000000000000000002ee6314f00000000000000000000
Outputs
1 output(s) for total of 19.432141354 ARQ
stealth address amount amount idx
00: 28e76c84ad70696aa324383f7ab922bdcf196f10c9a6889d467c2fbf2c40bc2e 19.432141354 435047 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": 88105, 
  "vin": [ {
      "gen": {
        "height": 88087
      }
    }
  ], 
  "vout": [ {
      "amount": 19432141354, 
      "target": {
        "key": "28e76c84ad70696aa324383f7ab922bdcf196f10c9a6889d467c2fbf2c40bc2e"
      }
    }
  ], 
  "extra": [ 1, 46, 105, 196, 14, 219, 78, 216, 128, 196, 19, 109, 104, 150, 217, 66, 254, 171, 119, 154, 201, 184, 187, 157, 206, 29, 183, 111, 139, 206, 229, 219, 166, 3, 33, 0, 208, 85, 177, 186, 20, 205, 222, 22, 229, 53, 231, 221, 80, 113, 143, 158, 245, 84, 172, 82, 244, 102, 163, 60, 148, 232, 60, 95, 249, 47, 195, 94, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 46, 230, 49, 79, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}