Transaction Details
Tx hash
dc012b2889af79330e9a0b9788c3b2e4911daa15b8e1a1063bc09812a7635d72
Tx prefix hash
586e0642d186fcecb7df2bf06a035306e2d27c5faf45e9b3b144f61fbefa4d9b
Tx public key
0fb7256c6b3d4dd5d7ee1afeb04ae4ed81853d5a6514469b4bfec6bfdd3fc9e0
Age [y:d:h:m:s]
05:168:19:22:04
Timestamp [UCT] (epoch)
2019-06-13 19:15:06 (1560453306)
Block
197879 (1402040 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
010fb7256c6b3d4dd5d7ee1afeb04ae4ed81853d5a6514469b4bfec6bfdd3fc9e002110000001a42e7bec6000000000000000000032100e48af87fe0a2f07a37d28770db172fe5e5c0fd7ad7f0f7f4711243cfd84b5949
Outputs
1 output(s) for total of 18.440888381 ARQ
stealth address amount amount idx
00: 9ae6a8f2f4e33cd9ec67c12f0cabfc14e3125f0b0f9fcdae5c5b42ff74ee77e1 18.440888381 895811 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": 197897, 
  "vin": [ {
      "gen": {
        "height": 197879
      }
    }
  ], 
  "vout": [ {
      "amount": 18440888381, 
      "target": {
        "key": "9ae6a8f2f4e33cd9ec67c12f0cabfc14e3125f0b0f9fcdae5c5b42ff74ee77e1"
      }
    }
  ], 
  "extra": [ 1, 15, 183, 37, 108, 107, 61, 77, 213, 215, 238, 26, 254, 176, 74, 228, 237, 129, 133, 61, 90, 101, 20, 70, 155, 75, 254, 198, 191, 221, 63, 201, 224, 2, 17, 0, 0, 0, 26, 66, 231, 190, 198, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 228, 138, 248, 127, 224, 162, 240, 122, 55, 210, 135, 112, 219, 23, 47, 229, 229, 192, 253, 122, 215, 240, 247, 244, 113, 18, 67, 207, 216, 75, 89, 73
  ], 
  "rct_signatures": {
    "type": 0
  }
}