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: 1ba4c1ec1f571f2f0db3a1734a1ba3852901956ab2f5cf43bc8e5cff75d541cd
Tx prefix hash: 0c1892f24457c752041a230faea4991c8bacc4b02ec37662099c2c1c99370669
Tx public key: ec54354607749267b984cdd8fbeda3a07bb0c646817ecd3fb30a6bbc8cd50e1f
| Timestamp: 1779904541 | Timestamp [UTC]: 2026-05-27 17:55:41 | Age [y:d:h:m:s]: 00:012:08:44:55 |
| Block: 3179 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4717 | RingCT/type: yes/0 |
| Extra: 01ec54354607749267b984cdd8fbeda3a07bb0c646817ecd3fb30a6bbc8cd50e1f02090000000226697be300 | ||
1 output(s) for total of 34.971744992720 HMNY
| stealth address | amount | amount idx | tag |
| 00: d160c218a3dd007e627fe6d717c51989be488f6caf4b4996981cc2a0e044bf36 | 34.971744992720 | 3805 of 0 | <11> |
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": 3239,
"vin": [ {
"gen": {
"height": 3179
}
}
],
"vout": [ {
"amount": 34971744992720,
"target": {
"tagged_key": {
"key": "d160c218a3dd007e627fe6d717c51989be488f6caf4b4996981cc2a0e044bf36",
"view_tag": "11"
}
}
}
],
"extra": [ 1, 236, 84, 53, 70, 7, 116, 146, 103, 185, 132, 205, 216, 251, 237, 163, 160, 123, 176, 198, 70, 129, 126, 205, 63, 179, 10, 107, 188, 140, 213, 14, 31, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}