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: 479ee7a0899cfc9d5ee68df8de6e340729ccca23ba82003d5a8ca0bdcb05dd65
Tx prefix hash: 19d81b8f6bf42cb8efb48230861d51bdb3f79c724e0f8d33098c3bc9aaba36a1
Tx public key: 7b663e617e92c01dcd361bda7ea44315fd1f247e1d089ba1f40cb3d5c6201c1c
| Timestamp: 1779457435 | Timestamp [UTC]: 2026-05-22 13:43:55 | Age [y:d:h:m:s]: 00:017:07:28:12 |
| Block: 401 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7485 | RingCT/type: yes/0 |
| Extra: 017b663e617e92c01dcd361bda7ea44315fd1f247e1d089ba1f40cb3d5c6201c1c02090000000193369e7d00 | ||
1 output(s) for total of 35.157538755161 HMNY
| stealth address | amount | amount idx | tag |
| 00: 559d8efd0ceadf6c1672c3b887a1c567402dedacbb53d27cbcd78979d8d77936 | 35.157538755161 | 403 of 0 | <29> |
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": 461,
"vin": [ {
"gen": {
"height": 401
}
}
],
"vout": [ {
"amount": 35157538755161,
"target": {
"tagged_key": {
"key": "559d8efd0ceadf6c1672c3b887a1c567402dedacbb53d27cbcd78979d8d77936",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 123, 102, 62, 97, 126, 146, 192, 29, 205, 54, 27, 218, 126, 164, 67, 21, 253, 31, 36, 126, 29, 8, 155, 161, 244, 12, 179, 213, 198, 32, 28, 28, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}