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: 36f694e8d6cc5bb276aa5e3ad732d43806bfd16ad6f5c07dc5f8a68da85fd164
Tx prefix hash: ec09f5d54dc1db83c5b03e771c1c3fae906be7e71d7360b3a6b19ef3459a0507
Tx public key: 1929d891587f10803a743b0cf45ebe4d9aaaa022119a4cbc548e7e702209f107
| Timestamp: 1779634800 | Timestamp [UTC]: 2026-05-24 15:00:00 | Age [y:d:h:m:s]: 00:015:11:40:36 |
| Block: 1047 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6849 | RingCT/type: yes/0 |
| Extra: 011929d891587f10803a743b0cf45ebe4d9aaaa022119a4cbc548e7e702209f107020900000001ba6d17be00 | ||
1 output(s) for total of 35.114246127270 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3598968a951db3f6c55cadf8ecf2f43bd0d62ef9c7a4eea4f0003cee29f38a7 | 35.114246127270 | 1185 of 0 | <ac> |
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": 1107,
"vin": [ {
"gen": {
"height": 1047
}
}
],
"vout": [ {
"amount": 35114246127270,
"target": {
"tagged_key": {
"key": "b3598968a951db3f6c55cadf8ecf2f43bd0d62ef9c7a4eea4f0003cee29f38a7",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 25, 41, 216, 145, 88, 127, 16, 128, 58, 116, 59, 12, 244, 94, 190, 77, 154, 170, 160, 34, 17, 154, 76, 188, 84, 142, 126, 112, 34, 9, 241, 7, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}