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: e69c13ef33687e9282b974fe51af8104bec91d2bc32556f290b252a66390404b
Tx prefix hash: 5084a5738a12bd8590dbf4d470c0032048c35642f08aa3aca287697e158ee23a
Tx public key: d1fb738202df9e39130838d7b0c12307a6f85b160ef5c2ea48241c61cf321683
| Timestamp: 1779438571 | Timestamp [UTC]: 2026-05-22 08:29:31 | Age [y:d:h:m:s]: 00:017:17:06:26 |
| Block: 191 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7695 | RingCT/type: yes/0 |
| Extra: 01d1fb738202df9e39130838d7b0c12307a6f85b160ef5c2ea48241c61cf3216830209000000025cddc08000 | ||
1 output(s) for total of 35.171623702751 HMNY
| stealth address | amount | amount idx | tag |
| 00: 339ae58ce415699ed1e2d2f530b94503f151b8b5b518283cac467a5879e39ee8 | 35.171623702751 | 187 of 0 | <d3> |
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": 251,
"vin": [ {
"gen": {
"height": 191
}
}
],
"vout": [ {
"amount": 35171623702751,
"target": {
"tagged_key": {
"key": "339ae58ce415699ed1e2d2f530b94503f151b8b5b518283cac467a5879e39ee8",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 209, 251, 115, 130, 2, 223, 158, 57, 19, 8, 56, 215, 176, 193, 35, 7, 166, 248, 91, 22, 14, 245, 194, 234, 72, 36, 28, 97, 207, 50, 22, 131, 2, 9, 0, 0, 0, 2, 92, 221, 192, 128, 0
],
"rct_signatures": {
"type": 0
}
}