Transaction Details
Tx hash
fff5d3ee803ee00047b9b1463a0f69c07337af4d7c9f6cb5be03fdc848c60e1d
Tx prefix hash
1ad8b0e024c5a03473e37b106a145f7cb14e933dff16da1f3a982ff92f0df12d
Tx public key
9f11d991e6631b63ef4976cfae943265dfa4e0901fd74d10d59344aaad09dc3e
Age [y:d:h:m:s]
05:261:01:12:21
Timestamp [UCT] (epoch)
2019-03-11 06:32:18 (1552285938)
Block
130455 (1467859 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019f11d991e6631b63ef4976cfae943265dfa4e0901fd74d10d59344aaad09dc3e032100d8a1102a5352a073f0fb89dd4cf2b72bdf8f70a4768f1c8b28760853374fd59a021b00000000000000000000000000b357b8d900000000000000000000
Outputs
1 output(s) for total of 19.043584502 ARQ
stealth address amount amount idx
00: 0e1e06cca9bbf90f97986410b0ad0b78b2a15fe7a3bbc022a7702d479a8d1583 19.043584502 619313 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": 130473, 
  "vin": [ {
      "gen": {
        "height": 130455
      }
    }
  ], 
  "vout": [ {
      "amount": 19043584502, 
      "target": {
        "key": "0e1e06cca9bbf90f97986410b0ad0b78b2a15fe7a3bbc022a7702d479a8d1583"
      }
    }
  ], 
  "extra": [ 1, 159, 17, 217, 145, 230, 99, 27, 99, 239, 73, 118, 207, 174, 148, 50, 101, 223, 164, 224, 144, 31, 215, 77, 16, 213, 147, 68, 170, 173, 9, 220, 62, 3, 33, 0, 216, 161, 16, 42, 83, 82, 160, 115, 240, 251, 137, 221, 76, 242, 183, 43, 223, 143, 112, 164, 118, 143, 28, 139, 40, 118, 8, 83, 55, 79, 213, 154, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 179, 87, 184, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}