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: 19a30b469d5a18b73e10d1163e6c3a5ae86c724c619b215aebc8ed001589ecbf
Tx prefix hash: 1e379eab91f4d494ef7a5641dd925c7e117b942b7b8aea1ddc2c77e1f10ec5e8
Tx public key: d44937864ce173dfa1bacb7d90f03ae8c7d4ec4554db5dd510ceb65229f71166
| Timestamp: 1780126046 | Timestamp [UTC]: 2026-05-30 07:27:26 | Age [y:d:h:m:s]: 00:009:18:08:31 |
| Block: 4914 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2972 | RingCT/type: yes/0 |
| Extra: 01d44937864ce173dfa1bacb7d90f03ae8c7d4ec4554db5dd510ceb65229f7116602090000000326697be300 | ||
1 output(s) for total of 34.856205918959 HMNY
| stealth address | amount | amount idx | tag |
| 00: d05ec836d75afe20d2175e31939104adb477dfc20134a430accb197304ab5b96 | 34.856205918959 | 6233 of 0 | <94> |
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": 4974,
"vin": [ {
"gen": {
"height": 4914
}
}
],
"vout": [ {
"amount": 34856205918959,
"target": {
"tagged_key": {
"key": "d05ec836d75afe20d2175e31939104adb477dfc20134a430accb197304ab5b96",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 212, 73, 55, 134, 76, 225, 115, 223, 161, 186, 203, 125, 144, 240, 58, 232, 199, 212, 236, 69, 84, 219, 93, 213, 16, 206, 182, 82, 41, 247, 17, 102, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}