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: c888d30ffe977b6e5c2e4098c075e1cb07a46c18f4fe56f0472b1cb5445c28b9
Tx prefix hash: 7b054e2882d568924ec671d12c4c2bee6c62a929cbfbc37e75688236a311f1b7
Tx public key: e9dbe99f2d730e88811709ae7ec562f43673d82b1662d5c6dcd32a8fc475b677
| Timestamp: 1779850844 | Timestamp [UTC]: 2026-05-27 03:00:44 | Age [y:d:h:m:s]: 00:012:21:46:03 |
| Block: 2525 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5361 | RingCT/type: yes/0 |
| Extra: 01e9dbe99f2d730e88811709ae7ec562f43673d82b1662d5c6dcd32a8fc475b67702090000000126697be300 | ||
1 output(s) for total of 35.015396218829 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3413f2dd22568b9d303e3df0990ce857dfe34e12399521ada45894191896a53 | 35.015396218829 | 2973 of 0 | <c6> |
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": 2585,
"vin": [ {
"gen": {
"height": 2525
}
}
],
"vout": [ {
"amount": 35015396218829,
"target": {
"tagged_key": {
"key": "b3413f2dd22568b9d303e3df0990ce857dfe34e12399521ada45894191896a53",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 233, 219, 233, 159, 45, 115, 14, 136, 129, 23, 9, 174, 126, 197, 98, 244, 54, 115, 216, 43, 22, 98, 213, 198, 220, 211, 42, 143, 196, 117, 182, 119, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}