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: 36c8f17be11f2713153cffa119c441f88cb6bb64c6f1183b372cd7a03c333c66
Tx prefix hash: d61d990c2ca337c3dba4b958c705aef47d9186b8418f1d1c4058dda92db728fe
Tx public key: 9b1d5aad4041836d4def00e9b0f4ccc995e69850a45bad55655e1d777dd791e0
| Timestamp: 1780116784 | Timestamp [UTC]: 2026-05-30 04:53:04 | Age [y:d:h:m:s]: 00:009:21:56:44 |
| Block: 4879 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3041 | RingCT/type: yes/0 |
| Extra: 019b1d5aad4041836d4def00e9b0f4ccc995e69850a45bad55655e1d777dd791e002090000000626697be300 | ||
1 output(s) for total of 34.861148901633 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4231b37a080f66375c6869c495fa2ad6c44d0d08b480f2d7a8c6473055bda57c | 34.861148901633 | 6169 of 0 | <c8> |
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": 4939,
"vin": [ {
"gen": {
"height": 4879
}
}
],
"vout": [ {
"amount": 34861148901633,
"target": {
"tagged_key": {
"key": "4231b37a080f66375c6869c495fa2ad6c44d0d08b480f2d7a8c6473055bda57c",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 155, 29, 90, 173, 64, 65, 131, 109, 77, 239, 0, 233, 176, 244, 204, 201, 149, 230, 152, 80, 164, 91, 173, 85, 101, 94, 29, 119, 125, 215, 145, 224, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}