Transaction Details
Tx hash
a9381614b463c4cf92503767cc3f2d8e2d69d9873f7932e9dcffb154751ecbf6
Tx prefix hash
393bbc2dea4c6dc9937934d0996bdb4d89a60ad75624d6fc733de1dd92808093
Tx public key
7d2dea5b4903d82cf8b22f77c5e8b6f9a3ca2d4d7284b4aa74875b3d42248fc9
Age [y:d:h:m:s]
05:316:08:34:15
Timestamp [UCT] (epoch)
2019-01-18 14:15:54 (1547820954)
Block
93526 (1507344 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1367 kB
Tx version
2
RingCT type
0
Extra
017d2dea5b4903d82cf8b22f77c5e8b6f9a3ca2d4d7284b4aa74875b3d42248fc9032107892967bd461410ed1fa0e81e7d7a40b44c99655e7cffb6cccb5f713faa4fae5502140000001445f1a500000000000000000000000000
Outputs
1 output(s) for total of 19.381708166 ARQ
stealth address amount amount idx
00: 7a2e626f7379f60f8450e84a6b7e890a7a1d7bbec4c183475bf56ceb5dae5705 19.381708166 461360 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": 93544, 
  "vin": [ {
      "gen": {
        "height": 93526
      }
    }
  ], 
  "vout": [ {
      "amount": 19381708166, 
      "target": {
        "key": "7a2e626f7379f60f8450e84a6b7e890a7a1d7bbec4c183475bf56ceb5dae5705"
      }
    }
  ], 
  "extra": [ 1, 125, 45, 234, 91, 73, 3, 216, 44, 248, 178, 47, 119, 197, 232, 182, 249, 163, 202, 45, 77, 114, 132, 180, 170, 116, 135, 91, 61, 66, 36, 143, 201, 3, 33, 7, 137, 41, 103, 189, 70, 20, 16, 237, 31, 160, 232, 30, 125, 122, 64, 180, 76, 153, 101, 94, 124, 255, 182, 204, 203, 95, 113, 63, 170, 79, 174, 85, 2, 20, 0, 0, 0, 20, 69, 241, 165, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}