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: c40dceecca0cc6a96753b2ed02adc0807ef1949cd171bb113c844e465e980b26
Tx prefix hash: 80ff3209f661750cf288af763c09af96b4d739d87e42153c9123a787b6c3abb6
Tx public key: 7e8a3bc435ddb1c3c7d7ec31dd62b3fd229ffd5338827d7ba6c7a2ba312ca3c9
| Timestamp: 1779461031 | Timestamp [UTC]: 2026-05-22 14:43:51 | Age [y:d:h:m:s]: 00:017:10:52:06 |
| Block: 436 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7450 | RingCT/type: yes/0 |
| Extra: 017e8a3bc435ddb1c3c7d7ec31dd62b3fd229ffd5338827d7ba6c7a2ba312ca3c902090000000293369e7d00 | ||
1 output(s) for total of 35.155191812340 HMNY
| stealth address | amount | amount idx | tag |
| 00: 422b70931d227100688395d3008654f19014179bc7977f7a0bdbe4f885e08b3b | 35.155191812340 | 440 of 0 | <a2> |
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": 496,
"vin": [ {
"gen": {
"height": 436
}
}
],
"vout": [ {
"amount": 35155191812340,
"target": {
"tagged_key": {
"key": "422b70931d227100688395d3008654f19014179bc7977f7a0bdbe4f885e08b3b",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 126, 138, 59, 196, 53, 221, 177, 195, 199, 215, 236, 49, 221, 98, 179, 253, 34, 159, 253, 83, 56, 130, 125, 123, 166, 199, 162, 186, 49, 44, 163, 201, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}