Transaction Details
Tx hash
fb9b8f72ecdc4bf7563b315d25615cfdb4951a0ac1bf4f0927b1e268f5088f8e
Tx prefix hash
21108bb774170568e1ee327488df5c0d2082bd9de9603a1a9ddd363b3d29b06a
Tx public key
931ae8ee682ef02370485f5c501f6750478ddf5759f2971c992cc60e6dcd6400
Age [y:d:h:m:s]
05:307:00:39:31
Timestamp [UCT] (epoch)
2019-01-27 03:44:56 (1548560696)
Block
99607 (1500734 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01931ae8ee682ef02370485f5c501f6750478ddf5759f2971c992cc60e6dcd6400032100f68c01a0aac80f5b4f242284f854ec67a8d326fce44be8e1e1f9ec64dc6504e1021b00000000000000000000000000026f93d700000000000000000000
Outputs
1 output(s) for total of 19.325736317 ARQ
stealth address amount amount idx
00: 3ed9f1bf352479463e19d49878d072a9ff59748a49f61ec919c373c4e207e51b 19.325736317 492235 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": 99625, 
  "vin": [ {
      "gen": {
        "height": 99607
      }
    }
  ], 
  "vout": [ {
      "amount": 19325736317, 
      "target": {
        "key": "3ed9f1bf352479463e19d49878d072a9ff59748a49f61ec919c373c4e207e51b"
      }
    }
  ], 
  "extra": [ 1, 147, 26, 232, 238, 104, 46, 240, 35, 112, 72, 95, 92, 80, 31, 103, 80, 71, 141, 223, 87, 89, 242, 151, 28, 153, 44, 198, 14, 109, 205, 100, 0, 3, 33, 0, 246, 140, 1, 160, 170, 200, 15, 91, 79, 36, 34, 132, 248, 84, 236, 103, 168, 211, 38, 252, 228, 75, 232, 225, 225, 249, 236, 100, 220, 101, 4, 225, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 111, 147, 215, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}