Transaction Details
Tx hash
bdf79199e45a88b4f3ce0a4e556bd152322b34e41c4e338de12f56ec64c08244
Tx prefix hash
566d25c7b30bfa9003fcdba8538919cd03d3609a2c244e93ffa45d51eadbdebc
Tx public key
8396d2331e66da26da77fc7c8549f6e41c2be871b2f2e0afede56f5dca0c2185
Age [y:d:h:m:s]
05:248:17:35:58
Timestamp [UCT] (epoch)
2019-03-22 20:00:33 (1553284833)
Block
138688 (1459071 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018396d2331e66da26da77fc7c8549f6e41c2be871b2f2e0afede56f5dca0c218503210015861908f61b9d5d1482f49140fc1c7ff81cf0fd60510c26cf7bbf67f2beb459021b00000000000000000000000000899b5a9700000000000000000000
Outputs
1 output(s) for total of 18.968787568 ARQ
stealth address amount amount idx
00: 3318e94d4192dc73dbb41b83e2012ce041e9252aca402184fd98999d45a12f95 18.968787568 643800 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": 138706, 
  "vin": [ {
      "gen": {
        "height": 138688
      }
    }
  ], 
  "vout": [ {
      "amount": 18968787568, 
      "target": {
        "key": "3318e94d4192dc73dbb41b83e2012ce041e9252aca402184fd98999d45a12f95"
      }
    }
  ], 
  "extra": [ 1, 131, 150, 210, 51, 30, 102, 218, 38, 218, 119, 252, 124, 133, 73, 246, 228, 28, 43, 232, 113, 178, 242, 224, 175, 237, 229, 111, 93, 202, 12, 33, 133, 3, 33, 0, 21, 134, 25, 8, 246, 27, 157, 93, 20, 130, 244, 145, 64, 252, 28, 127, 248, 28, 240, 253, 96, 81, 12, 38, 207, 123, 191, 103, 242, 190, 180, 89, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 137, 155, 90, 151, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}