Transaction Details
Tx hash
870e44c9eb53d96d1dd4796b63601f0400c034edd6b753643e164f841b894198
Tx prefix hash
97747127d4bb65b334bf99a8e839e924a450060e33841bd8f43b67416c40fc60
Tx public key
7b43a1e97bd28df7dde31d831708d22d93b6feff31e704e2b61e37e36088485e
Age [y:d:h:m:s]
05:325:16:01:53
Timestamp [UCT] (epoch)
2019-01-09 00:46:34 (1546994794)
Block
86706 (1513998 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
017b43a1e97bd28df7dde31d831708d22d93b6feff31e704e2b61e37e36088485e0321005f7a639c5fdf1f8148af8e97ffe8858e69414e44d82954b9289a8c0c58133f58021000000004de1f0e000000000000000000
Outputs
1 output(s) for total of 19.444918465 ARQ
stealth address amount amount idx
00: 5a3fdc4a44c45cc1e37dc15f653ec84648cf513b28d0eb9dd52eb5304e42811c 19.444918465 428423 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": 86724, 
  "vin": [ {
      "gen": {
        "height": 86706
      }
    }
  ], 
  "vout": [ {
      "amount": 19444918465, 
      "target": {
        "key": "5a3fdc4a44c45cc1e37dc15f653ec84648cf513b28d0eb9dd52eb5304e42811c"
      }
    }
  ], 
  "extra": [ 1, 123, 67, 161, 233, 123, 210, 141, 247, 221, 227, 29, 131, 23, 8, 210, 45, 147, 182, 254, 255, 49, 231, 4, 226, 182, 30, 55, 227, 96, 136, 72, 94, 3, 33, 0, 95, 122, 99, 156, 95, 223, 31, 129, 72, 175, 142, 151, 255, 232, 133, 142, 105, 65, 78, 68, 216, 41, 84, 185, 40, 154, 140, 12, 88, 19, 63, 88, 2, 16, 0, 0, 0, 4, 222, 31, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}