Transaction Details
Tx hash
4c2b4e4e3c4569083e2e461d01721ac3fd00d1b28d0b6efb45d7fe4fd45423e9
Tx prefix hash
86458ff5a0534a32eec20336b9be52f6fe5d78a6ac5303f0ad5644f5d9ae3f52
Tx public key
de25bd7cc7da533a7cedb17f68f6acd7a578bf7fd1a7a14eec13dccdee437dce
Age [y:d:h:m:s]
05:313:00:31:01
Timestamp [UCT] (epoch)
2019-01-21 18:35:26 (1548095726)
Block
95822 (1504942 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01de25bd7cc7da533a7cedb17f68f6acd7a578bf7fd1a7a14eec13dccdee437dce03210007207a0265b4853a4536cf6d5ae5e3c4499f7d9891b0d6630f7891e427ed7da6021b000000000000000000000000003d9fa3f100000000000000000000
Outputs
1 output(s) for total of 19.360500328 ARQ
stealth address amount amount idx
00: 08121b6d0e197d7d2eac1fa4d997a8180faf9ad283e43a39f0e71753330ad26b 19.360500328 473066 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": 95840, 
  "vin": [ {
      "gen": {
        "height": 95822
      }
    }
  ], 
  "vout": [ {
      "amount": 19360500328, 
      "target": {
        "key": "08121b6d0e197d7d2eac1fa4d997a8180faf9ad283e43a39f0e71753330ad26b"
      }
    }
  ], 
  "extra": [ 1, 222, 37, 189, 124, 199, 218, 83, 58, 124, 237, 177, 127, 104, 246, 172, 215, 165, 120, 191, 127, 209, 167, 161, 78, 236, 19, 220, 205, 238, 67, 125, 206, 3, 33, 0, 7, 32, 122, 2, 101, 180, 133, 58, 69, 54, 207, 109, 90, 229, 227, 196, 73, 159, 125, 152, 145, 176, 214, 99, 15, 120, 145, 228, 39, 237, 125, 166, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 61, 159, 163, 241, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}