Transaction Details
Tx hash
5044dbd399fca0c9320bbd8013b9cb2108af1784919f0ddb509d5e5cd3eb79a6
Tx prefix hash
dccfedca0c45a64554c34ffede12c6807fc23a423e6dca381d62d995e6d046a0
Tx public key
46da4e195336c8b76d6100f7534f157320b3daf622004f8a4053762f281882e5
Age [y:d:h:m:s]
05:263:11:11:04
Timestamp [UCT] (epoch)
2019-03-10 00:34:23 (1552178063)
Block
129565 (1469570 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0146da4e195336c8b76d6100f7534f157320b3daf622004f8a4053762f281882e5032100d2b96261170ee95d6f951f95a8b7e9da8dce6ca4409797159e637ce5ebbf583b021b000000000000000000000000009f38c4e800000000000000000000
Outputs
1 output(s) for total of 19.051485075 ARQ
stealth address amount amount idx
00: b60f3537a7024f9be617b249a430794fee4585ecbf7a81b3873da71449d3df76 19.051485075 616481 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": 129583, 
  "vin": [ {
      "gen": {
        "height": 129565
      }
    }
  ], 
  "vout": [ {
      "amount": 19051485075, 
      "target": {
        "key": "b60f3537a7024f9be617b249a430794fee4585ecbf7a81b3873da71449d3df76"
      }
    }
  ], 
  "extra": [ 1, 70, 218, 78, 25, 83, 54, 200, 183, 109, 97, 0, 247, 83, 79, 21, 115, 32, 179, 218, 246, 34, 0, 79, 138, 64, 83, 118, 47, 40, 24, 130, 229, 3, 33, 0, 210, 185, 98, 97, 23, 14, 233, 93, 111, 149, 31, 149, 168, 183, 233, 218, 141, 206, 108, 164, 64, 151, 151, 21, 158, 99, 124, 229, 235, 191, 88, 59, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 159, 56, 196, 232, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}