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: b49e5aaed1d7eaee341e527747235265c25222835365b1f72dfe4a26e46a2017
Tx prefix hash: 76c7b350fee1d54be05fc4f94395ccc51cdeb151d5ab9d3f1dd7b806992ff7ef
Tx public key: 98d4d56a63207fb0aa3488a132314421363a455a151317170e574564de3847a7
| Timestamp: 1780691228 | Timestamp [UTC]: 2026-06-05 20:27:08 | Age [y:d:h:m:s]: 00:011:11:38:13 |
| Block: 5713 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3032 | RingCT/type: yes/0 |
| Extra: 0198d4d56a63207fb0aa3488a132314421363a455a151317170e574564de3847a7020900000001e49593ff00 | ||
1 output(s) for total of 34.803126457979 HMNY
| stealth address | amount | amount idx | tag |
| 00: ca70fb0380f35461cb39eb193ed70f4a892bae776cd873c7817b6b70a1161795 | 34.803126457979 | 7164 of 0 | <76> |
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": 5773,
"vin": [ {
"gen": {
"height": 5713
}
}
],
"vout": [ {
"amount": 34803126457979,
"target": {
"tagged_key": {
"key": "ca70fb0380f35461cb39eb193ed70f4a892bae776cd873c7817b6b70a1161795",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 152, 212, 213, 106, 99, 32, 127, 176, 170, 52, 136, 161, 50, 49, 68, 33, 54, 58, 69, 90, 21, 19, 23, 23, 14, 87, 69, 100, 222, 56, 71, 167, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}