Transaction Details
Tx hash
efb1f8e46589e717c9b54f936ccd95a7335f115eb24e065521ca5b01770aebe6
Tx prefix hash
bc85c36256bcccaeb48096a706319c71e023b9f5e639dbd1aacf1191a2849d43
Tx public key
8690880dc547db1d5d21ef784cc9baa52597956231949938f1538d8d862c5e76
Age [y:d:h:m:s]
05:100:11:41:31
Timestamp [UCT] (epoch)
2019-08-23 14:09:57 (1566569397)
Block
248647 (1353007 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018690880dc547db1d5d21ef784cc9baa52597956231949938f1538d8d862c5e76032100414908040dca418bb0e39acdb943e2fc8490199b7612d3f8d2ec53c88e2c1bb7021b000000000000000000000000026149380e00000000000000000000
Outputs
1 output(s) for total of 20.431181322 ARQ
stealth address amount amount idx
00: 9ea20abbad7f17bf4827a5485c0c91038eaddad26acfc5661e15d3e7b30525ce 20.431181322 1111926 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": 248665, 
  "vin": [ {
      "gen": {
        "height": 248647
      }
    }
  ], 
  "vout": [ {
      "amount": 20431181322, 
      "target": {
        "key": "9ea20abbad7f17bf4827a5485c0c91038eaddad26acfc5661e15d3e7b30525ce"
      }
    }
  ], 
  "extra": [ 1, 134, 144, 136, 13, 197, 71, 219, 29, 93, 33, 239, 120, 76, 201, 186, 165, 37, 151, 149, 98, 49, 148, 153, 56, 241, 83, 141, 141, 134, 44, 94, 118, 3, 33, 0, 65, 73, 8, 4, 13, 202, 65, 139, 176, 227, 154, 205, 185, 67, 226, 252, 132, 144, 25, 155, 118, 18, 211, 248, 210, 236, 83, 200, 142, 44, 27, 183, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 97, 73, 56, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}