Transaction Details
Tx hash
e37024c787c6cfeb3e4a807c28355d40973b797e59f6df948f265cfdce499f3e
Tx prefix hash
8abb7f9bd7aab9b5d035bbaf9e796db4e2e7c36009042cf818d888c9128fe4ed
Tx public key
08c6e7f0c5b610be7e04a1e13bdc00e0b0fcee4ba83d29b3ec087dd61e6fc79a
Age [y:d:h:m:s]
05:201:13:51:02
Timestamp [UCT] (epoch)
2019-03-16 16:39:26 (1552754366)
Block
134300 (1425904 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0108c6e7f0c5b610be7e04a1e13bdc00e0b0fcee4ba83d29b3ec087dd61e6fc79a03210067754ba897c514f27b4fc4f992fee8732361d5453dce5adaa21d6dd53343cba7021b00000000000000000000000000024e15fb00000000000000000000
Outputs
1 output(s) for total of 19.008518689 ARQ
stealth address amount amount idx
00: 2a6edb4df7c51b6c3db68f22dbb0070a213d3da32c5c7d948dbd33d0592fc3d9 19.008518689 631501 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": 134318, 
  "vin": [ {
      "gen": {
        "height": 134300
      }
    }
  ], 
  "vout": [ {
      "amount": 19008518689, 
      "target": {
        "key": "2a6edb4df7c51b6c3db68f22dbb0070a213d3da32c5c7d948dbd33d0592fc3d9"
      }
    }
  ], 
  "extra": [ 1, 8, 198, 231, 240, 197, 182, 16, 190, 126, 4, 161, 225, 59, 220, 0, 224, 176, 252, 238, 75, 168, 61, 41, 179, 236, 8, 125, 214, 30, 111, 199, 154, 3, 33, 0, 103, 117, 75, 168, 151, 197, 20, 242, 123, 79, 196, 249, 146, 254, 232, 115, 35, 97, 213, 69, 61, 206, 90, 218, 162, 29, 109, 213, 51, 67, 203, 167, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 78, 21, 251, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}