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: d17ba553aeed149d9c490061dce13a13f0ef5df37446808074d37b60e5cfa4a3
Tx prefix hash: 037ddd03a017754809801eca755317a9e9bb0bdd24d727aa535040743bc8a076
Tx public key: 62a30b0ca62cabdba70f3db10d6f57f04379498e2cf8a9a5744c44554da8fcab
| Timestamp: 1781000793 | Timestamp [UTC]: 2026-06-09 10:26:33 | Age [y:d:h:m:s]: 00:007:22:09:41 |
| Block: 8443 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 302 | RingCT/type: yes/0 |
| Extra: 0162a30b0ca62cabdba70f3db10d6f57f04379498e2cf8a9a5744c44554da8fcab020900000001e49593ff00 | ||
1 output(s) for total of 34.622375256165 HMNY
| stealth address | amount | amount idx | tag |
| 00: 85e18fd86a31a0f370ff8f8c8d4018e03a4738a53d7d83f72a999f1b54fb98b2 | 34.622375256165 | 10433 of 0 | <c5> |
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": 8503,
"vin": [ {
"gen": {
"height": 8443
}
}
],
"vout": [ {
"amount": 34622375256165,
"target": {
"tagged_key": {
"key": "85e18fd86a31a0f370ff8f8c8d4018e03a4738a53d7d83f72a999f1b54fb98b2",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 98, 163, 11, 12, 166, 44, 171, 219, 167, 15, 61, 177, 13, 111, 87, 240, 67, 121, 73, 142, 44, 248, 169, 165, 116, 76, 68, 85, 77, 168, 252, 171, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}