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: 4519e52611a85bab7557a6ce3ae7c82a821fc09e7aa03ddbd019f066ef70ab91
Tx prefix hash: b3d3555b855ec447beaa0fd2c046985c7e7d6e8e88ffdc57e86b8901d3a9c23c
Tx public key: 56e06e86abf4b23f7120b02bc511b55893efc933c0c076e7307dfa6ded1e110f
| Timestamp: 1780692831 | Timestamp [UTC]: 2026-06-05 20:53:51 | Age [y:d:h:m:s]: 00:003:04:42:06 |
| Block: 5821 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2065 | RingCT/type: yes/0 |
| Extra: 0156e06e86abf4b23f7120b02bc511b55893efc933c0c076e7307dfa6ded1e110f020900000001e49593ff00 | ||
1 output(s) for total of 34.795957966367 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9f321bd5a04a449d37ffa4a42515d2c1e3122893a9b97de21e70200956c5365a | 34.795957966367 | 7278 of 0 | <d1> |
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": 5881,
"vin": [ {
"gen": {
"height": 5821
}
}
],
"vout": [ {
"amount": 34795957966367,
"target": {
"tagged_key": {
"key": "9f321bd5a04a449d37ffa4a42515d2c1e3122893a9b97de21e70200956c5365a",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 86, 224, 110, 134, 171, 244, 178, 63, 113, 32, 176, 43, 197, 17, 181, 88, 147, 239, 201, 51, 192, 192, 118, 231, 48, 125, 250, 109, 237, 30, 17, 15, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}