Transaction Details
Tx hash
098409526169720d31f90a112ee8050d9e5b6ca2b2aef9cc28c15d384b603eb5
Tx prefix hash
a13823683860830952045d372803241d5588d9da137359f66480e5f9d5c7e003
Tx public key
84f4f0b51a4722cd592763b5c055d66747c626f68c86649f085ff9a2a9c25399
Age [y:d:h:m:s]
05:273:20:42:07
Timestamp [UCT] (epoch)
2019-01-07 22:42:05 (1546900925)
Block
85951 (1477430 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0184f4f0b51a4722cd592763b5c055d66747c626f68c86649f085ff9a2a9c25399032100315ca4e5821c547e424d5c9fd7c4c2e557c69237bb6a734adce7aadff6ada03e021b000000000000000000000000000b005aac00000000000000000000
Outputs
1 output(s) for total of 19.451842304 ARQ
stealth address amount amount idx
00: 9889ca0ec6bba8933fbabf2111fb49e27cde76d8ab7622eae273ec419917f140 19.451842304 425020 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": 85969, 
  "vin": [ {
      "gen": {
        "height": 85951
      }
    }
  ], 
  "vout": [ {
      "amount": 19451842304, 
      "target": {
        "key": "9889ca0ec6bba8933fbabf2111fb49e27cde76d8ab7622eae273ec419917f140"
      }
    }
  ], 
  "extra": [ 1, 132, 244, 240, 181, 26, 71, 34, 205, 89, 39, 99, 181, 192, 85, 214, 103, 71, 198, 38, 246, 140, 134, 100, 159, 8, 95, 249, 162, 169, 194, 83, 153, 3, 33, 0, 49, 92, 164, 229, 130, 28, 84, 126, 66, 77, 92, 159, 215, 196, 194, 229, 87, 198, 146, 55, 187, 106, 115, 74, 220, 231, 170, 223, 246, 173, 160, 62, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 0, 90, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}