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: 2a1918c1d5dd512fd805015fb92093b6ab8917f2303b6509a175331255b47424
Tx prefix hash: f011739dc0e6e30e33fa7387443126be4ba42f7bec2003b1f8fa413236d26b44
Tx public key: 3e0658dae487ff78d12094aa4c39c5328c3cefd2937a316aaf86812d08da360c
| Timestamp: 1779436728 | Timestamp [UTC]: 2026-05-22 07:58:48 | Age [y:d:h:m:s]: 00:017:19:52:10 |
| Block: 146 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7807 | RingCT/type: yes/0 |
| Extra: 013e0658dae487ff78d12094aa4c39c5328c3cefd2937a316aaf86812d08da360c020900000001a662ed0300 | ||
1 output(s) for total of 35.174642639864 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5c53cc64f245cf479dde4a8fea5111b8816adda72a226bbbcada7a4312aa7a37 | 35.174642639864 | 142 of 0 | <7d> |
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": 206,
"vin": [ {
"gen": {
"height": 146
}
}
],
"vout": [ {
"amount": 35174642639864,
"target": {
"tagged_key": {
"key": "5c53cc64f245cf479dde4a8fea5111b8816adda72a226bbbcada7a4312aa7a37",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 62, 6, 88, 218, 228, 135, 255, 120, 209, 32, 148, 170, 76, 57, 197, 50, 140, 60, 239, 210, 147, 122, 49, 106, 175, 134, 129, 45, 8, 218, 54, 12, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}