Transaction Details
Tx hash
1ffefd93c79653bffa44d1dec845d1b87d6a5e58b01ae8bbd21d1036cd4c23e3
Tx prefix hash
25d711fe4e146e8fc76f17582e3f4154428655d145851018ed0a5989a6429933
Tx public key
bc1a39d78aff0215859880b0f848289900003fff45df53fbcbd2e8f1822f1ca4
Age [y:d:h:m:s]
05:274:11:03:49
Timestamp [UCT] (epoch)
2019-02-27 14:34:46 (1551278086)
Block
122106 (1477424 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bc1a39d78aff0215859880b0f848289900003fff45df53fbcbd2e8f1822f1ca403210064fb95c2f3df8c33afaa5d6ba59405ca29616e3add27f89450d8c223b6775b4a021b0000000000000000000000000091b34b1000000000000000000000
Outputs
1 output(s) for total of 19.119389424 ARQ
stealth address amount amount idx
00: cbde65163d08cfe213800b3788368fd46c6c897d2bf15cdd82ff092beefdecf0 19.119389424 588201 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": 122124, 
  "vin": [ {
      "gen": {
        "height": 122106
      }
    }
  ], 
  "vout": [ {
      "amount": 19119389424, 
      "target": {
        "key": "cbde65163d08cfe213800b3788368fd46c6c897d2bf15cdd82ff092beefdecf0"
      }
    }
  ], 
  "extra": [ 1, 188, 26, 57, 215, 138, 255, 2, 21, 133, 152, 128, 176, 248, 72, 40, 153, 0, 0, 63, 255, 69, 223, 83, 251, 203, 210, 232, 241, 130, 47, 28, 164, 3, 33, 0, 100, 251, 149, 194, 243, 223, 140, 51, 175, 170, 93, 107, 165, 148, 5, 202, 41, 97, 110, 58, 221, 39, 248, 148, 80, 216, 194, 35, 182, 119, 91, 74, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 145, 179, 75, 16, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}