Transaction Details
Tx hash
4dea8ac7e8104a96e8eebf7b0f44b9de2913d220fcc0c93c739fd05b590d29cf
Tx prefix hash
dc8bddb97992544162de0de93453ffc335994d868bfb25fb7db31ec918a7302e
Tx public key
4074a4f3a3fe2c325377c2d0b779b9a2fb9f3ba89d2da92aa3a80a62cb6a41b8
Age [y:d:h:m:s]
05:238:00:37:10
Timestamp [UCT] (epoch)
2019-04-02 18:53:18 (1554231198)
Block
146451 (1451487 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014074a4f3a3fe2c325377c2d0b779b9a2fb9f3ba89d2da92aa3a80a62cb6a41b80321001259b143b3218814e5414b0d6bc9a77ad531c2bb2e49f4de2658afe22fcd85c9021b000000000000000000000000003b968e9c00000000000000000000
Outputs
1 output(s) for total of 18.898791559 ARQ
stealth address amount amount idx
00: b62e5f158d8c465eb96effd67d054eaa03b80b1e0c98beaf55e6f9a4a4b41ae9 18.898791559 672753 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": 146469, 
  "vin": [ {
      "gen": {
        "height": 146451
      }
    }
  ], 
  "vout": [ {
      "amount": 18898791559, 
      "target": {
        "key": "b62e5f158d8c465eb96effd67d054eaa03b80b1e0c98beaf55e6f9a4a4b41ae9"
      }
    }
  ], 
  "extra": [ 1, 64, 116, 164, 243, 163, 254, 44, 50, 83, 119, 194, 208, 183, 121, 185, 162, 251, 159, 59, 168, 157, 45, 169, 42, 163, 168, 10, 98, 203, 106, 65, 184, 3, 33, 0, 18, 89, 177, 67, 179, 33, 136, 20, 229, 65, 75, 13, 107, 201, 167, 122, 213, 49, 194, 187, 46, 73, 244, 222, 38, 88, 175, 226, 47, 205, 133, 201, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 59, 150, 142, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}