Transaction Details
Tx hash
147f6058aec2217e379e8397a0d6ebbca64d6ce89087358785959922ea3e4cd4
Tx prefix hash
03170c24c67089e76a8eae6fa0563bb6637e8629cf6e9da2e15e95d95198296c
Tx public key
6ff8544630c136f3d0c55e420e263382db80af7b7a7df62a39bbaf1a66305de9
Age [y:d:h:m:s]
05:269:06:59:16
Timestamp [UCT] (epoch)
2019-01-10 23:19:12 (1547162352)
Block
88073 (1474202 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1367 kB
Tx version
2
RingCT type
0
Extra
016ff8544630c136f3d0c55e420e263382db80af7b7a7df62a39bbaf1a66305de9032107b046a93e64b29a537424b17610ac5817b5244ced9229dfe62e0383559706b8e702140000000b1804a200000000000000000000000000
Outputs
1 output(s) for total of 19.432169938 ARQ
stealth address amount amount idx
00: 868a01fbef0d036d856df612b635c1195df3e5bc97c724f7d38ca16fdb0f6c55 19.432169938 434970 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": 88091, 
  "vin": [ {
      "gen": {
        "height": 88073
      }
    }
  ], 
  "vout": [ {
      "amount": 19432169938, 
      "target": {
        "key": "868a01fbef0d036d856df612b635c1195df3e5bc97c724f7d38ca16fdb0f6c55"
      }
    }
  ], 
  "extra": [ 1, 111, 248, 84, 70, 48, 193, 54, 243, 208, 197, 94, 66, 14, 38, 51, 130, 219, 128, 175, 123, 122, 125, 246, 42, 57, 187, 175, 26, 102, 48, 93, 233, 3, 33, 7, 176, 70, 169, 62, 100, 178, 154, 83, 116, 36, 177, 118, 16, 172, 88, 23, 181, 36, 76, 237, 146, 41, 223, 230, 46, 3, 131, 85, 151, 6, 184, 231, 2, 20, 0, 0, 0, 11, 24, 4, 162, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}