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: 082366c02dc0beb469409c1a720155708479e3ac1abeff22aea138825964e775
Tx prefix hash: da6210be0576f223abde806fd8abe31aa26ad51d3b5ca4392b0e0e35b0a29155
Tx public key: 967097548b4f515e04ab8a94dec570c436319fa41ce30643f00af5aa5b017f99
| Timestamp: 1779465805 | Timestamp [UTC]: 2026-05-22 16:03:25 | Age [y:d:h:m:s]: 00:017:11:47:33 |
| Block: 506 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7461 | RingCT/type: yes/0 |
| Extra: 01967097548b4f515e04ab8a94dec570c436319fa41ce30643f00af5aa5b017f9902090000000293369e7d00 | ||
1 output(s) for total of 35.150498396697 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5916944a562eea6c385a6f1d388c04432090ea4798b48a859232ca9b9ac988b5 | 35.150498396697 | 510 of 0 | <c6> |
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": 566,
"vin": [ {
"gen": {
"height": 506
}
}
],
"vout": [ {
"amount": 35150498396697,
"target": {
"tagged_key": {
"key": "5916944a562eea6c385a6f1d388c04432090ea4798b48a859232ca9b9ac988b5",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 150, 112, 151, 84, 139, 79, 81, 94, 4, 171, 138, 148, 222, 197, 112, 196, 54, 49, 159, 164, 28, 227, 6, 67, 240, 10, 245, 170, 91, 1, 127, 153, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}