Transaction Details
Tx hash
3dbfb058130d6371fcab55193178f36664067fcbd442e1993ce5a53153a37f4e
Tx prefix hash
e40164b6392fa4639f720d5c92531e00d6929713906db0a95ea504821c084044
Tx public key
b6b92e6abe1ee599c5d79a6cd9bc87565c93379ed0131662f1d0d5587bb8abea
Age [y:d:h:m:s]
04:361:04:30:59
Timestamp [UCT] (epoch)
2019-10-06 04:56:29 (1570337789)
Block
279426 (1279451 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01b6b92e6abe1ee599c5d79a6cd9bc87565c93379ed0131662f1d0d5587bb8abea02110000052c9778aae1000000000000000000032100657f818fefd97086d90d54bb37ec7aa838e0922767e94c2dce937a61997a2eaa
Outputs
1 output(s) for total of 20.133511301 ARQ
stealth address amount amount idx
00: 2add1f2f7f05da1e9d172964a4bfb4979e81451f0a040cb3d07d0c4095f3da30 20.133511301 1257876 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": 279444, 
  "vin": [ {
      "gen": {
        "height": 279426
      }
    }
  ], 
  "vout": [ {
      "amount": 20133511301, 
      "target": {
        "key": "2add1f2f7f05da1e9d172964a4bfb4979e81451f0a040cb3d07d0c4095f3da30"
      }
    }
  ], 
  "extra": [ 1, 182, 185, 46, 106, 190, 30, 229, 153, 197, 215, 154, 108, 217, 188, 135, 86, 92, 147, 55, 158, 208, 19, 22, 98, 241, 208, 213, 88, 123, 184, 171, 234, 2, 17, 0, 0, 5, 44, 151, 120, 170, 225, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 101, 127, 129, 143, 239, 217, 112, 134, 217, 13, 84, 187, 55, 236, 122, 168, 56, 224, 146, 39, 103, 233, 76, 45, 206, 147, 122, 97, 153, 122, 46, 170
  ], 
  "rct_signatures": {
    "type": 0
  }
}