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: 71460681ecb793dc3c399506c73fdd57094530c291789aa52ff64a5687c06057
Tx prefix hash: 350da7d15f581ce3cc8886bf3e717cc4b45e9d11a2b56d4d0b707e5d0e024635
Tx public key: fb5c2a7be4f61832238c3f03fb29acca1f8ea6da07ae35458694b6fdf99d2265
| Timestamp: 1779972122 | Timestamp [UTC]: 2026-05-28 12:42:02 | Age [y:d:h:m:s]: 00:011:15:08:56 |
| Block: 3855 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4097 | RingCT/type: yes/0 |
| Extra: 01fb5c2a7be4f61832238c3f03fb29acca1f8ea6da07ae35458694b6fdf99d226502090000000326697be300 | ||
1 output(s) for total of 34.926682569445 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8430aadc1e3bd490431443fd2c38edc380bebfe29fd8bb1bf51bca1fec5fa81e | 34.926682569445 | 4710 of 0 | <50> |
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": 3915,
"vin": [ {
"gen": {
"height": 3855
}
}
],
"vout": [ {
"amount": 34926682569445,
"target": {
"tagged_key": {
"key": "8430aadc1e3bd490431443fd2c38edc380bebfe29fd8bb1bf51bca1fec5fa81e",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 251, 92, 42, 123, 228, 246, 24, 50, 35, 140, 63, 3, 251, 41, 172, 202, 31, 142, 166, 218, 7, 174, 53, 69, 134, 148, 182, 253, 249, 157, 34, 101, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}