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: f4df5495e84936069b26dcb77010a4408004dccdf9b965fee8aaa6fbfe5b193d
Tx prefix hash: 4dc2a669b2ea75ae478670eadf5b447dbdb4c202594ce1829a62964ed4e0154f
Tx public key: 63f07d69db4518d523e878947cd8993fd20629328546cf9fa03d69a5a6af151c
| Timestamp: 1779464795 | Timestamp [UTC]: 2026-05-22 15:46:35 | Age [y:d:h:m:s]: 00:017:09:00:12 |
| Block: 491 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7395 | RingCT/type: yes/0 |
| Extra: 0163f07d69db4518d523e878947cd8993fd20629328546cf9fa03d69a5a6af151c02090000000393369e7d00 | ||
1 output(s) for total of 35.151504075868 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74704cce3569602aaec936c57fe6287f1f9fed90084918df1f329ceaae962e1a | 35.151504075868 | 495 of 0 | <36> |
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": 551,
"vin": [ {
"gen": {
"height": 491
}
}
],
"vout": [ {
"amount": 35151504075868,
"target": {
"tagged_key": {
"key": "74704cce3569602aaec936c57fe6287f1f9fed90084918df1f329ceaae962e1a",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 99, 240, 125, 105, 219, 69, 24, 213, 35, 232, 120, 148, 124, 216, 153, 63, 210, 6, 41, 50, 133, 70, 207, 159, 160, 61, 105, 165, 166, 175, 21, 28, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}