Transaction Details
Tx hash
dba87330b6ec15b10d77b59113ffe8098e49b339d539c3c859465e4aac8642c0
Tx prefix hash
fd4a98f68753ac960835dfec541d95220661aef6aa4efb56f6758b53ce2d7e91
Tx public key
42246eeb5a8843290fc1e0c231c1e33f06f3ce88e80e10c1981f0966b1d6fa4b
Age [y:d:h:m:s]
05:331:14:03:19
Timestamp [UCT] (epoch)
2018-12-30 09:45:44 (1546163144)
Block
79853 (1518221 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0142246eeb5a8843290fc1e0c231c1e33f06f3ce88e80e10c1981f0966b1d6fa4b03210048f73334f78a1393f48af2e92b48c9ee83490c9757e8693ec3804239eb2541c6021b000000000000000000000000001ddf439d00000000000000000000
Outputs
1 output(s) for total of 19.508532643 ARQ
stealth address amount amount idx
00: f925f6d7080bab8adc57cc8af960da322280b713319c619504a831107ad25268 19.508532643 395859 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": 79871, 
  "vin": [ {
      "gen": {
        "height": 79853
      }
    }
  ], 
  "vout": [ {
      "amount": 19508532643, 
      "target": {
        "key": "f925f6d7080bab8adc57cc8af960da322280b713319c619504a831107ad25268"
      }
    }
  ], 
  "extra": [ 1, 66, 36, 110, 235, 90, 136, 67, 41, 15, 193, 224, 194, 49, 193, 227, 63, 6, 243, 206, 136, 232, 14, 16, 193, 152, 31, 9, 102, 177, 214, 250, 75, 3, 33, 0, 72, 247, 51, 52, 247, 138, 19, 147, 244, 138, 242, 233, 43, 72, 201, 238, 131, 73, 12, 151, 87, 232, 105, 62, 195, 128, 66, 57, 235, 37, 65, 198, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 29, 223, 67, 157, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}