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: 58c68a0ecd1ee305193dc8b4841e80f246cebe45d300bde5b255005504c3a5a7
Tx prefix hash: 1d651449cc255233acf61e6fd1a8d51288251004f136bd449bf315b5c11eb714
Tx public key: 60ef9cb0deefefb2ace1e07d45c412f5ac4d402d5ed1d5f0b2ac8db3ec4e2411
| Timestamp: 1779922632 | Timestamp [UTC]: 2026-05-27 22:57:12 | Age [y:d:h:m:s]: 00:012:01:49:35 |
| Block: 3360 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4526 | RingCT/type: yes/0 |
| Extra: 0160ef9cb0deefefb2ace1e07d45c412f5ac4d402d5ed1d5f0b2ac8db3ec4e241102090000000426697be300 | ||
1 output(s) for total of 34.959673765894 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2e2ff362ce3b44954b4942610b56e9eb4e9a8a05b385e08ded888d93e533c38f | 34.959673765894 | 4047 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": 3420,
"vin": [ {
"gen": {
"height": 3360
}
}
],
"vout": [ {
"amount": 34959673765894,
"target": {
"tagged_key": {
"key": "2e2ff362ce3b44954b4942610b56e9eb4e9a8a05b385e08ded888d93e533c38f",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 96, 239, 156, 176, 222, 239, 239, 178, 172, 225, 224, 125, 69, 196, 18, 245, 172, 77, 64, 45, 94, 209, 213, 240, 178, 172, 141, 179, 236, 78, 36, 17, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}