Transaction Details
Tx hash
07e014e7431cb36c23d7a82035885b07d43b79317d412d34b3e8591f8b23c2f3
Tx prefix hash
117f40c419cffff5093cb7107c83cbf8b46343e55d520f5e7138688e4f245b8b
Tx public key
c89d98945e7d48a41a6f3f7f6b0d42fc9def7ef4c4d8e64d39857a1073683f04
Age [y:d:h:m:s]
05:040:20:37:57
Timestamp [UCT] (epoch)
2019-10-19 22:48:42 (1571525322)
Block
289181 (1310884 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01c89d98945e7d48a41a6f3f7f6b0d42fc9def7ef4c4d8e64d39857a1073683f04021100000012ebc0569e00000002000001fa00032100c8667c2106a1450eebf2a19c025efc60ddebb403a8e7eb32e12d4d0d0189cff7
Outputs
1 output(s) for total of 20.040122211 ARQ
stealth address amount amount idx
00: 0b9a6739d030284597e89e89449197377f0a6578ad6e30c4f3c9a4d3bb3dfc3b 20.040122211 1304602 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": 289199, 
  "vin": [ {
      "gen": {
        "height": 289181
      }
    }
  ], 
  "vout": [ {
      "amount": 20040122211, 
      "target": {
        "key": "0b9a6739d030284597e89e89449197377f0a6578ad6e30c4f3c9a4d3bb3dfc3b"
      }
    }
  ], 
  "extra": [ 1, 200, 157, 152, 148, 94, 125, 72, 164, 26, 111, 63, 127, 107, 13, 66, 252, 157, 239, 126, 244, 196, 216, 230, 77, 57, 133, 122, 16, 115, 104, 63, 4, 2, 17, 0, 0, 0, 18, 235, 192, 86, 158, 0, 0, 0, 2, 0, 0, 1, 250, 0, 3, 33, 0, 200, 102, 124, 33, 6, 161, 69, 14, 235, 242, 161, 156, 2, 94, 252, 96, 221, 235, 180, 3, 168, 231, 235, 50, 225, 45, 77, 13, 1, 137, 207, 247
  ], 
  "rct_signatures": {
    "type": 0
  }
}