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: be2e30a2e3647ecaddf85372c6ea49f03dacad3b0f6ea7473f02dfc7779188c8
Tx prefix hash: d15a4fe2144ae724119d6ba36e83df5c90d8064ffb45dc109efbdb45a820b85f
Tx public key: 298277d728f40a20e034b4fdb039ac4c7a9a787630365e509a145fca1d26ce3f
| Timestamp: 1779437911 | Timestamp [UTC]: 2026-05-22 08:18:31 | Age [y:d:h:m:s]: 00:017:17:17:26 |
| Block: 178 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7708 | RingCT/type: yes/0 |
| Extra: 01298277d728f40a20e034b4fdb039ac4c7a9a787630365e509a145fca1d26ce3f020900000001a662ed0300 | ||
1 output(s) for total of 35.172495813523 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff506e83c8e50b5fc9d41f122acb6564c6fda9eb065be4f46129b62805cec1b2 | 35.172495813523 | 174 of 0 | <15> |
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": 238,
"vin": [ {
"gen": {
"height": 178
}
}
],
"vout": [ {
"amount": 35172495813523,
"target": {
"tagged_key": {
"key": "ff506e83c8e50b5fc9d41f122acb6564c6fda9eb065be4f46129b62805cec1b2",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 41, 130, 119, 215, 40, 244, 10, 32, 224, 52, 180, 253, 176, 57, 172, 76, 122, 154, 120, 118, 48, 54, 94, 80, 154, 20, 95, 202, 29, 38, 206, 63, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}