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: 12f905ab0bc92a9afd7e222a8fd41034c13664ef2b746b68242c7585905838da
Tx prefix hash: 8a85a8e2fecc396f29f57045b30d34469cdff696f8bf1c12083a4d8a816fea13
Tx public key: e9e46927c4f13047b4eec0cca43100656aac7007c71c2ef164810a15e2dfb0d4
| Timestamp: 1779629701 | Timestamp [UTC]: 2026-05-24 13:35:01 | Age [y:d:h:m:s]: 00:015:13:14:47 |
| Block: 844 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7056 | RingCT/type: yes/0 |
| Extra: 01e9e46927c4f13047b4eec0cca43100656aac7007c71c2ef164810a15e2dfb0d4020900000001ba6d17be00 | ||
1 output(s) for total of 35.127844719897 HMNY
| stealth address | amount | amount idx | tag |
| 00: cee45fe35cc0a427b860b3e287c7c3d004d3ef9045e6863eb9966e9a252e1027 | 35.127844719897 | 976 of 0 | <ee> |
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": 904,
"vin": [ {
"gen": {
"height": 844
}
}
],
"vout": [ {
"amount": 35127844719897,
"target": {
"tagged_key": {
"key": "cee45fe35cc0a427b860b3e287c7c3d004d3ef9045e6863eb9966e9a252e1027",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 233, 228, 105, 39, 196, 241, 48, 71, 180, 238, 192, 204, 164, 49, 0, 101, 106, 172, 112, 7, 199, 28, 46, 241, 100, 129, 10, 21, 226, 223, 176, 212, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}