Transaction Details
Tx hash
270aa3f382a95cdda4615958b8fdadfa21456f0c4252ae8f3ade984cb52324d9
Tx prefix hash
1cb0c7d1d0b753a857bc37a99b9a2cca69dc1062ada66d529e9b0eeff7064d00
Tx public key
753e137f84d5a8d7fb92084a89cd692b08bc37a0dfa0457b42be8e9024ddd6b1
Age [y:d:h:m:s]
05:143:11:27:44
Timestamp [UCT] (epoch)
2019-07-06 03:54:34 (1562385274)
Block
213859 (1383971 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01753e137f84d5a8d7fb92084a89cd692b08bc37a0dfa0457b42be8e9024ddd6b10321005f7a7f319ab25dae7406e18364477af36dd94ff5e7d9c2bd7d4f04b1e99a2aef021b000000000000000000000000002ca00d3c00000000000000000000
Outputs
1 output(s) for total of 18.300905403 ARQ
stealth address amount amount idx
00: 1226cfa311b463e9db576aa770b2ac0d1cd5b8d5de4284590e3d222043fb1da9 18.300905403 989688 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": 213877, 
  "vin": [ {
      "gen": {
        "height": 213859
      }
    }
  ], 
  "vout": [ {
      "amount": 18300905403, 
      "target": {
        "key": "1226cfa311b463e9db576aa770b2ac0d1cd5b8d5de4284590e3d222043fb1da9"
      }
    }
  ], 
  "extra": [ 1, 117, 62, 19, 127, 132, 213, 168, 215, 251, 146, 8, 74, 137, 205, 105, 43, 8, 188, 55, 160, 223, 160, 69, 123, 66, 190, 142, 144, 36, 221, 214, 177, 3, 33, 0, 95, 122, 127, 49, 154, 178, 93, 174, 116, 6, 225, 131, 100, 71, 122, 243, 109, 217, 79, 245, 231, 217, 194, 189, 125, 79, 4, 177, 233, 154, 42, 239, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 44, 160, 13, 60, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}