Transaction Details
Tx hash
b841be95ead56ed63c127469808dac0c3bf6f437dec4c70def9fbae618c2b4a9
Tx prefix hash
80f49e6f582f214c329042e7e7eb2d8f02d3a7a8be63a570e6868771623687f5
Tx public key
4f027e422d538b9c7c3e9fe59bc62e97b07a0f713977bb7a39bf90f6cfe1b819
Age [y:d:h:m:s]
05:187:09:03:30
Timestamp [UCT] (epoch)
2019-04-04 01:27:46 (1554341266)
Block
147367 (1415745 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014f027e422d538b9c7c3e9fe59bc62e97b07a0f713977bb7a39bf90f6cfe1b819032100f005d437111b685e5a25cd784c3b4a34d0a751e92ea3962d35bf0a983e8a71cb021b000000000000000000000000001b9c3e8400000000000000000000
Outputs
1 output(s) for total of 18.890448011 ARQ
stealth address amount amount idx
00: 3e8c10b7455c8397fb66a574a82bd134244ad430daa8dc9d37517e23f1cab619 18.890448011 676632 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": 147385, 
  "vin": [ {
      "gen": {
        "height": 147367
      }
    }
  ], 
  "vout": [ {
      "amount": 18890448011, 
      "target": {
        "key": "3e8c10b7455c8397fb66a574a82bd134244ad430daa8dc9d37517e23f1cab619"
      }
    }
  ], 
  "extra": [ 1, 79, 2, 126, 66, 45, 83, 139, 156, 124, 62, 159, 229, 155, 198, 46, 151, 176, 122, 15, 113, 57, 119, 187, 122, 57, 191, 144, 246, 207, 225, 184, 25, 3, 33, 0, 240, 5, 212, 55, 17, 27, 104, 94, 90, 37, 205, 120, 76, 59, 74, 52, 208, 167, 81, 233, 46, 163, 150, 45, 53, 191, 10, 152, 62, 138, 113, 203, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 27, 156, 62, 132, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}