Transaction Details
Tx hash
a0d946f9d161f42b2bc34897557ab4d16703aa9542ec8b59dfa7abc67e1db5fd
Tx prefix hash
88874fccc112045af868055380f759b117b5279fb2edf5a7c98a42043a8165a8
Tx public key
68571e14ca222017b79815519e94ca2d7678e2e6bcebe0b6da29e8e8c9254ab4
Age [y:d:h:m:s]
05:235:07:11:39
Timestamp [UCT] (epoch)
2019-04-07 01:33:48 (1554600828)
Block
149471 (1449577 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0168571e14ca222017b79815519e94ca2d7678e2e6bcebe0b6da29e8e8c9254ab4032100e5a0bbe67dc203b9aa6b9c840412299659e5517c7c2b0888db067750f387438e021b000000000000000000000000003611a68800000000000000000000
Outputs
1 output(s) for total of 18.871505378 ARQ
stealth address amount amount idx
00: b9fd87b2cfbce7a33091ed0f21ea79c2f15798af571363d4efcb3a6c1a3a397b 18.871505378 684628 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": 149489, 
  "vin": [ {
      "gen": {
        "height": 149471
      }
    }
  ], 
  "vout": [ {
      "amount": 18871505378, 
      "target": {
        "key": "b9fd87b2cfbce7a33091ed0f21ea79c2f15798af571363d4efcb3a6c1a3a397b"
      }
    }
  ], 
  "extra": [ 1, 104, 87, 30, 20, 202, 34, 32, 23, 183, 152, 21, 81, 158, 148, 202, 45, 118, 120, 226, 230, 188, 235, 224, 182, 218, 41, 232, 232, 201, 37, 74, 180, 3, 33, 0, 229, 160, 187, 230, 125, 194, 3, 185, 170, 107, 156, 132, 4, 18, 41, 150, 89, 229, 81, 124, 124, 43, 8, 136, 219, 6, 119, 80, 243, 135, 67, 142, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 54, 17, 166, 136, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}