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: 52c1ad6ba2d4668602034232a4998e26504b2b48f33f6e4a151191ce045526fc
Tx prefix hash: 716b6f690ac93c1ecf357c20ea7e20a10942ee748e3fe74419ffb7a62e99da4a
Tx public key: 085a5350efc6c76b806727bc35f236d875cda8f1f61b1a8399f81a1553f62c95
| Timestamp: 1779777254 | Timestamp [UTC]: 2026-05-26 06:34:14 | Age [y:d:h:m:s]: 00:013:20:15:34 |
| Block: 2077 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5832 | RingCT/type: yes/0 |
| Extra: 01085a5350efc6c76b806727bc35f236d875cda8f1f61b1a8399f81a1553f62c9502090000000626697be300 | ||
1 output(s) for total of 35.045329416908 HMNY
| stealth address | amount | amount idx | tag |
| 00: 278b90369270a8758c00a857a85dad0293b1b53d0056e7df92857e1f272bb7f6 | 35.045329416908 | 2383 of 0 | <3c> |
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": 2137,
"vin": [ {
"gen": {
"height": 2077
}
}
],
"vout": [ {
"amount": 35045329416908,
"target": {
"tagged_key": {
"key": "278b90369270a8758c00a857a85dad0293b1b53d0056e7df92857e1f272bb7f6",
"view_tag": "3c"
}
}
}
],
"extra": [ 1, 8, 90, 83, 80, 239, 198, 199, 107, 128, 103, 39, 188, 53, 242, 54, 216, 117, 205, 168, 241, 246, 27, 26, 131, 153, 248, 26, 21, 83, 246, 44, 149, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}