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: cb2c4d100a2662b21cd2235bd39c2eb53f09bd9fe7e9203564b4272e044fd02a
Tx prefix hash: f5197350ae968647bfbe700ebc618bfbc0911f2b02afe08d831764918ec981e4
Tx public key: 4f101c38cb33e65a6fc190268a8b3d78c41c82f032ca88b1003145cdb9a5f0ff
| Timestamp: 1780701897 | Timestamp [UTC]: 2026-06-05 23:24:57 | Age [y:d:h:m:s]: 00:002:21:47:10 |
| Block: 6067 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1819 | RingCT/type: yes/0 |
| Extra: 014f101c38cb33e65a6fc190268a8b3d78c41c82f032ca88b1003145cdb9a5f0ff020900000001e49593ff00 | ||
1 output(s) for total of 34.779635246851 HMNY
| stealth address | amount | amount idx | tag |
| 00: 76e475d3f629abe77f851033d3f439404d4b84f5569639e3888f56af13a8981a | 34.779635246851 | 7538 of 0 | <67> |
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": 6127,
"vin": [ {
"gen": {
"height": 6067
}
}
],
"vout": [ {
"amount": 34779635246851,
"target": {
"tagged_key": {
"key": "76e475d3f629abe77f851033d3f439404d4b84f5569639e3888f56af13a8981a",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 79, 16, 28, 56, 203, 51, 230, 90, 111, 193, 144, 38, 138, 139, 61, 120, 196, 28, 130, 240, 50, 202, 136, 177, 0, 49, 69, 205, 185, 165, 240, 255, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}