Transaction Details
Tx hash
dca90b40f20d9fb13d27f5856266b08c710bfd9c584d40965c02a20f405c99ab
Tx prefix hash
5476ddc8d2412b92df10bf1695920f5a442b7de00f4c011fab162dd96be19446
Tx public key
3b0c408dfb54f9d1f0a295c5c6ec9a7d4314366b5cdb1fe0b51cb186e3c503f4
Age [y:d:h:m:s]
05:156:12:43:16
Timestamp [UCT] (epoch)
2019-06-17 21:00:06 (1560805206)
Block
200793 (1393307 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
013b0c408dfb54f9d1f0a295c5c6ec9a7d4314366b5cdb1fe0b51cb186e3c503f403210074b2e83874ee0c8d8488bd68926db9d119c34f271c587d413b98d54e15865ff8021b000000000000000000000000001f8b465d00000000000000000000
Outputs
1 output(s) for total of 18.415282490 ARQ
stealth address amount amount idx
00: a956eabf8964978114f8f5f6b7a4bbb554f3dc885e8b835ad34e7269cde278e8 18.415282490 912560 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": 200811, 
  "vin": [ {
      "gen": {
        "height": 200793
      }
    }
  ], 
  "vout": [ {
      "amount": 18415282490, 
      "target": {
        "key": "a956eabf8964978114f8f5f6b7a4bbb554f3dc885e8b835ad34e7269cde278e8"
      }
    }
  ], 
  "extra": [ 1, 59, 12, 64, 141, 251, 84, 249, 209, 240, 162, 149, 197, 198, 236, 154, 125, 67, 20, 54, 107, 92, 219, 31, 224, 181, 28, 177, 134, 227, 197, 3, 244, 3, 33, 0, 116, 178, 232, 56, 116, 238, 12, 141, 132, 136, 189, 104, 146, 109, 185, 209, 25, 195, 79, 39, 28, 88, 125, 65, 59, 152, 213, 78, 21, 134, 95, 248, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 31, 139, 70, 93, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}