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: 392cc365da1d5db65c8c9c681d78b031a1424bb429361b510549c9cd8c221ed5
Tx prefix hash: 21dc251ed3a963985ad04b9be81569c2d6434811cfa031cc715403f0a3d75392
Tx public key: e2513e54ad659f0cc2aa11131b4d11848f4e5404e4f9f733f5d8eb09c30b818a
| Timestamp: 1779723667 | Timestamp [UTC]: 2026-05-25 15:41:07 | Age [y:d:h:m:s]: 00:014:11:08:41 |
| Block: 1806 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6114 | RingCT/type: yes/0 |
| Extra: 01e2513e54ad659f0cc2aa11131b4d11848f4e5404e4f9f733f5d8eb09c30b818a020900000003ba6d17be00 | ||
1 output(s) for total of 35.063448748820 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3a31315ad365034211f1833f424e610d15ad61ed56d66dbc95b498212dea54ea | 35.063448748820 | 1998 of 0 | <26> |
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": 1866,
"vin": [ {
"gen": {
"height": 1806
}
}
],
"vout": [ {
"amount": 35063448748820,
"target": {
"tagged_key": {
"key": "3a31315ad365034211f1833f424e610d15ad61ed56d66dbc95b498212dea54ea",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 226, 81, 62, 84, 173, 101, 159, 12, 194, 170, 17, 19, 27, 77, 17, 132, 143, 78, 84, 4, 228, 249, 247, 51, 245, 216, 235, 9, 195, 11, 129, 138, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}