Transaction Details
Tx hash
d44a6508eb43ed247bf92b6cd77584d0037a53acf5bd77461cd0c4ee0792661d
Tx prefix hash
cb0c5a5d3d36ef1b3ba2cacb13e28038e9462c988057c612f9ef86db08103246
Tx public key
a753ab52204f05893ca1c5d4039950e511bb0477bd56004220e9f30e050be1f8
Age [y:d:h:m:s]
05:245:14:53:10
Timestamp [UCT] (epoch)
2019-03-29 08:58:16 (1553849896)
Block
143294 (1456904 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a753ab52204f05893ca1c5d4039950e511bb0477bd56004220e9f30e050be1f803210057809a7ac49483ef1bdf404631041d27e56c38d8a310278de94234ffab6c363b021b000000000000000000000000001ff8923b00000000000000000000
Outputs
1 output(s) for total of 18.927330870 ARQ
stealth address amount amount idx
00: 6b1a9a40989c1311b9c1ef667c97cb4bc10f47a78895cb5ee036220f5589e3b6 18.927330870 659162 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": 143312, 
  "vin": [ {
      "gen": {
        "height": 143294
      }
    }
  ], 
  "vout": [ {
      "amount": 18927330870, 
      "target": {
        "key": "6b1a9a40989c1311b9c1ef667c97cb4bc10f47a78895cb5ee036220f5589e3b6"
      }
    }
  ], 
  "extra": [ 1, 167, 83, 171, 82, 32, 79, 5, 137, 60, 161, 197, 212, 3, 153, 80, 229, 17, 187, 4, 119, 189, 86, 0, 66, 32, 233, 243, 14, 5, 11, 225, 248, 3, 33, 0, 87, 128, 154, 122, 196, 148, 131, 239, 27, 223, 64, 70, 49, 4, 29, 39, 229, 108, 56, 216, 163, 16, 39, 141, 233, 66, 52, 255, 171, 108, 54, 59, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 31, 248, 146, 59, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}