Transaction Details
Tx hash
3390ad861c89f63f5c78e22035bde8a5535c9735e73737c38d00d44fca8c31ac
Tx prefix hash
72f22d91db106642845c31d5ef2b9f7534e0a7c4168e5080f3f208a77fd9fe51
Tx public key
29d0c9a38b3e618b499bf98d3f9524c0c422f9c183fbff5254699d273de6a3a1
Age [y:d:h:m:s]
05:264:17:11:26
Timestamp [UCT] (epoch)
2019-03-07 13:40:01 (1551966001)
Block
127818 (1470471 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0129d0c9a38b3e618b499bf98d3f9524c0c422f9c183fbff5254699d273de6a3a1032100f2f8d4f71b4ac7d9fedd4313ee0128bcc94983c16d5c0155fbdfd95b1cdbe5d0021b000000000000000000000000002be3c26500000000000000000000
Outputs
1 output(s) for total of 19.067362235 ARQ
stealth address amount amount idx
00: 6fb41ee3dd43fbe39d1f4bfaace98c1e8da29b82a9d4ef9935a65ca1dc99bf1d 19.067362235 610148 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": 127836, 
  "vin": [ {
      "gen": {
        "height": 127818
      }
    }
  ], 
  "vout": [ {
      "amount": 19067362235, 
      "target": {
        "key": "6fb41ee3dd43fbe39d1f4bfaace98c1e8da29b82a9d4ef9935a65ca1dc99bf1d"
      }
    }
  ], 
  "extra": [ 1, 41, 208, 201, 163, 139, 62, 97, 139, 73, 155, 249, 141, 63, 149, 36, 192, 196, 34, 249, 193, 131, 251, 255, 82, 84, 105, 157, 39, 61, 230, 163, 161, 3, 33, 0, 242, 248, 212, 247, 27, 74, 199, 217, 254, 221, 67, 19, 238, 1, 40, 188, 201, 73, 131, 193, 109, 92, 1, 85, 251, 223, 217, 91, 28, 219, 229, 208, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 43, 227, 194, 101, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}