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: 0b603cde75def9b12e4fbe24e58ad646f4bc418e8d19c87d02bcf71be20aba22
Tx prefix hash: c1c1313ef20994c8219d5a067e99b44943854e6fda73c61b21c0307ed792536b
Tx public key: 0c6d8696ed05652c672ad9220a888eea6659f46c5931ebf005d36eb9aa45259e
| Timestamp: 1780323481 | Timestamp [UTC]: 2026-06-01 14:18:01 | Age [y:d:h:m:s]: 00:008:02:51:02 |
| Block: 5151 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3583 | RingCT/type: yes/0 |
| Extra: 010c6d8696ed05652c672ad9220a888eea6659f46c5931ebf005d36eb9aa45259e02090000002c26697be300 | ||
1 output(s) for total of 34.840453008690 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7fe017ce6972bc8ca2d7f66f08262d1a14be47c45205184aab199120bad1f3b | 34.840453008690 | 6526 of 0 | <12> |
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": 5211,
"vin": [ {
"gen": {
"height": 5151
}
}
],
"vout": [ {
"amount": 34840453008690,
"target": {
"tagged_key": {
"key": "d7fe017ce6972bc8ca2d7f66f08262d1a14be47c45205184aab199120bad1f3b",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 12, 109, 134, 150, 237, 5, 101, 44, 103, 42, 217, 34, 10, 136, 142, 234, 102, 89, 244, 108, 89, 49, 235, 240, 5, 211, 110, 185, 170, 69, 37, 158, 2, 9, 0, 0, 0, 44, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}