For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 3be189a5b6bb9c0fb8e25340ea3c2de75d2f35aa6954eb0457e512d4578b5ea3
Tx prefix hash: 2d860b137d345c07fd7f29d8c6cefcee2cd196df54ad7dbb0f1f702e50609d8f
Tx public key: 35e592fcaa2b485ea18cb72bd8726cb2d7ba13103b1d96a6b125bf2e22057434
| Timestamp: 1779804648 | Timestamp [UTC]: 2026-05-26 14:10:48 | Age [y:d:h:m:s]: 00:013:14:22:14 |
| Block: 2336 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5684 | RingCT/type: yes/0 |
| Extra: 0135e592fcaa2b485ea18cb72bd8726cb2d7ba13103b1d96a6b125bf2e2205743402090000000126697be300 | ||
1 output(s) for total of 35.028021167681 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc2f3da5c79db6e383d1b78719e736c053b3cbffbdd069cfc9c7c16b82edcb92 | 35.028021167681 | 2734 of 0 | <b5> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
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": 2396,
"vin": [ {
"gen": {
"height": 2336
}
}
],
"vout": [ {
"amount": 35028021167681,
"target": {
"tagged_key": {
"key": "fc2f3da5c79db6e383d1b78719e736c053b3cbffbdd069cfc9c7c16b82edcb92",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 53, 229, 146, 252, 170, 43, 72, 94, 161, 140, 183, 43, 216, 114, 108, 178, 215, 186, 19, 16, 59, 29, 150, 166, 177, 37, 191, 46, 34, 5, 116, 52, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}