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: eb078fb6b99ea32cac6d9b987a810df56d0e6ee250a200433f9f0426077f88b1
Tx prefix hash: 127fa519791b15aaf63031b72bccf3b55acc3e05a56ca95ef4ed7f2d7633abe2
Tx public key: 5517a1cf467c8e0ef0f769d0608d1f4431332f5dc57e48ff4719583adcb03f2b
| Timestamp: 1779630147 | Timestamp [UTC]: 2026-05-24 13:42:27 | Age [y:d:h:m:s]: 00:015:11:04:20 |
| Block: 862 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7024 | RingCT/type: yes/0 |
| Extra: 015517a1cf467c8e0ef0f769d0608d1f4431332f5dc57e48ff4719583adcb03f2b020900000001ba6d17be00 | ||
1 output(s) for total of 35.126638720610 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4be4b3cc5e60e8fb19a885146b364574af90bda1926394fa1fda5d5bddf48e7c | 35.126638720610 | 994 of 0 | <94> |
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": 922,
"vin": [ {
"gen": {
"height": 862
}
}
],
"vout": [ {
"amount": 35126638720610,
"target": {
"tagged_key": {
"key": "4be4b3cc5e60e8fb19a885146b364574af90bda1926394fa1fda5d5bddf48e7c",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 85, 23, 161, 207, 70, 124, 142, 14, 240, 247, 105, 208, 96, 141, 31, 68, 49, 51, 47, 93, 197, 126, 72, 255, 71, 25, 88, 58, 220, 176, 63, 43, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}