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: 30124e1562b76a91c96e15b34931ce82ac3e211634fdf9d377dee994ddc6f119
Tx prefix hash: 285d9c8d772ab98d0ae44a445adae38e27e5e96098a2feacf0e5a6fcccfbbc5e
Tx public key: ca7b36138005cb43a4eca122221561515da59b6a1a1bcaea290de4ce39c5f7da
| Timestamp: 1779436891 | Timestamp [UTC]: 2026-05-22 08:01:31 | Age [y:d:h:m:s]: 00:017:18:48:17 |
| Block: 150 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7770 | RingCT/type: yes/0 |
| Extra: 01ca7b36138005cb43a4eca122221561515da59b6a1a1bcaea290de4ce39c5f7da020900000001a662ed0300 | ||
1 output(s) for total of 35.174374279405 HMNY
| stealth address | amount | amount idx | tag |
| 00: 91a34e35ce0a1f1495f54c49ff1bcf83eb5c770008d41af62976751ac22c9813 | 35.174374279405 | 146 of 0 | <83> |
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": 210,
"vin": [ {
"gen": {
"height": 150
}
}
],
"vout": [ {
"amount": 35174374279405,
"target": {
"tagged_key": {
"key": "91a34e35ce0a1f1495f54c49ff1bcf83eb5c770008d41af62976751ac22c9813",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 202, 123, 54, 19, 128, 5, 203, 67, 164, 236, 161, 34, 34, 21, 97, 81, 93, 165, 155, 106, 26, 27, 202, 234, 41, 13, 228, 206, 57, 197, 247, 218, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}