Transaction Details
Tx hash
ff102a5ce32f57db772c849481e5e4f7ca50030d75db2ae3699c71dbe12e8de9
Tx prefix hash
8b3b54bf905e0ecebe550b3f750930fdaf0b319d38ef3e44c9abf16043fbd905
Tx public key
2c715a9515a396cc61f34c90e40fd0d405a48c2aeeb1e3da150eb2704df8f38c
Age [y:d:h:m:s]
05:148:01:47:28
Timestamp [UCT] (epoch)
2019-07-05 16:58:58 (1562345938)
Block
213522 (1387231 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
012c715a9515a396cc61f34c90e40fd0d405a48c2aeeb1e3da150eb2704df8f38c0211000000f3f20f8dbf000000000000000000032100fde4a59f0e1d1912d01adbe2e62591067e71e860b1d4c5d160f1b4dcd4ac29c0
Outputs
1 output(s) for total of 18.303927118 ARQ
stealth address amount amount idx
00: d8eecb0a3e8480e283386f9cb8f9e35b789a93b6770f8967f23bdd274a47b2a2 18.303927118 987756 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": 213540, 
  "vin": [ {
      "gen": {
        "height": 213522
      }
    }
  ], 
  "vout": [ {
      "amount": 18303927118, 
      "target": {
        "key": "d8eecb0a3e8480e283386f9cb8f9e35b789a93b6770f8967f23bdd274a47b2a2"
      }
    }
  ], 
  "extra": [ 1, 44, 113, 90, 149, 21, 163, 150, 204, 97, 243, 76, 144, 228, 15, 208, 212, 5, 164, 140, 42, 238, 177, 227, 218, 21, 14, 178, 112, 77, 248, 243, 140, 2, 17, 0, 0, 0, 243, 242, 15, 141, 191, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 253, 228, 165, 159, 14, 29, 25, 18, 208, 26, 219, 226, 230, 37, 145, 6, 126, 113, 232, 96, 177, 212, 197, 209, 96, 241, 180, 220, 212, 172, 41, 192
  ], 
  "rct_signatures": {
    "type": 0
  }
}