Transaction Details
Tx hash
ef02c00af04451b239ad3e683cef4b6fad07c76807971fc13f6dd8f4385e0cda
Tx prefix hash
b5f536cc192de81e4ecd3ca72dfecc357d484de13c788435cc117206602f342b
Tx public key
407688d177b757ead0e514b7e877666e96e0d66852a76b1e1f1601cd65a9c582
Age [y:d:h:m:s]
05:142:12:11:25
Timestamp [UCT] (epoch)
2019-08-05 15:16:02 (1565018162)
Block
235799 (1382102 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01407688d177b757ead0e514b7e877666e96e0d66852a76b1e1f1601cd65a9c582032100707b388d27d04ee82ba3286152da9940e5be9f2c512ce9f9a541f25e0540bc9c021b0000000000000000000000000e7ca5dd6800000000000000000000
Outputs
1 output(s) for total of 18.110442841 ARQ
stealth address amount amount idx
00: a7d7cabf8c119271c733736611ceed19f6cd77e88943c0b4a57d9eb23acfbc0b 18.110442841 1087718 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": 235817, 
  "vin": [ {
      "gen": {
        "height": 235799
      }
    }
  ], 
  "vout": [ {
      "amount": 18110442841, 
      "target": {
        "key": "a7d7cabf8c119271c733736611ceed19f6cd77e88943c0b4a57d9eb23acfbc0b"
      }
    }
  ], 
  "extra": [ 1, 64, 118, 136, 209, 119, 183, 87, 234, 208, 229, 20, 183, 232, 119, 102, 110, 150, 224, 214, 104, 82, 167, 107, 30, 31, 22, 1, 205, 101, 169, 197, 130, 3, 33, 0, 112, 123, 56, 141, 39, 208, 78, 232, 43, 163, 40, 97, 82, 218, 153, 64, 229, 190, 159, 44, 81, 44, 233, 249, 165, 65, 242, 94, 5, 64, 188, 156, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 14, 124, 165, 221, 104, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}