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: 9962cf8f609979bb7debdef014fa45951ccebc3676ade800d4e315387723ba9a
Tx prefix hash: 360ace71e34088186c4bac6165dd88a849cbb7db01733199a20286ad6fde3a2a
Tx public key: 14781b9bf4cf962d7ba1d5223e1cecf59c44d80259a7fef203a3b65e7c3f859d
| Timestamp: 1780729370 | Timestamp [UTC]: 2026-06-06 07:02:50 | Age [y:d:h:m:s]: 00:011:01:19:29 |
| Block: 6301 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2444 | RingCT/type: yes/0 |
| Extra: 0114781b9bf4cf962d7ba1d5223e1cecf59c44d80259a7fef203a3b65e7c3f859d020900000001e49593ff00 | ||
1 output(s) for total of 34.764115863412 HMNY
| stealth address | amount | amount idx | tag |
| 00: a41d6f48333f33a2d5e4d885c44332e936465303f99e2de407ee9e462ce0f031 | 34.764115863412 | 7786 of 0 | <e2> |
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": 6361,
"vin": [ {
"gen": {
"height": 6301
}
}
],
"vout": [ {
"amount": 34764115863412,
"target": {
"tagged_key": {
"key": "a41d6f48333f33a2d5e4d885c44332e936465303f99e2de407ee9e462ce0f031",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 20, 120, 27, 155, 244, 207, 150, 45, 123, 161, 213, 34, 62, 28, 236, 245, 156, 68, 216, 2, 89, 167, 254, 242, 3, 163, 182, 94, 124, 63, 133, 157, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}