Transaction Details
Tx hash
601d1b7b4e0705fe83c3a3a66ed75abe1b0aefd542d5e14d3ca1c03aaddfe254
Tx prefix hash
4c41dccc1b5cbe3c237eae42406158f788a72ad97273fc883d707fa8f7f4fc5b
Tx public key
46d2e7d6413f8dfb2b7a8f8d319d80a824b18668bf5b0c79fe57e19b22aa8d43
Age [y:d:h:m:s]
05:190:00:09:56
Timestamp [UCT] (epoch)
2019-05-24 13:14:31 (1558703671)
Block
183441 (1417165 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0146d2e7d6413f8dfb2b7a8f8d319d80a824b18668bf5b0c79fe57e19b22aa8d430321006848c4e1c5800e1f711d8c8354e1192f51595682bb12778d005177469d2fc91d021b00000000000000000000000000ac748bc600000000000000000000
Outputs
1 output(s) for total of 18.568284118 ARQ
stealth address amount amount idx
00: fee343bf25b5ba0028cb6932f3f7a38cdfcc9a4de4a91f8d0ef03ae2dd912464 18.568284118 824517 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": 183459, 
  "vin": [ {
      "gen": {
        "height": 183441
      }
    }
  ], 
  "vout": [ {
      "amount": 18568284118, 
      "target": {
        "key": "fee343bf25b5ba0028cb6932f3f7a38cdfcc9a4de4a91f8d0ef03ae2dd912464"
      }
    }
  ], 
  "extra": [ 1, 70, 210, 231, 214, 65, 63, 141, 251, 43, 122, 143, 141, 49, 157, 128, 168, 36, 177, 134, 104, 191, 91, 12, 121, 254, 87, 225, 155, 34, 170, 141, 67, 3, 33, 0, 104, 72, 196, 225, 197, 128, 14, 31, 113, 29, 140, 131, 84, 225, 25, 47, 81, 89, 86, 130, 187, 18, 119, 141, 0, 81, 119, 70, 157, 47, 201, 29, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 172, 116, 139, 198, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}