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: da2d272e4106498de66d9a0994bdee9b8bed18a9041fda1aac72cc686b124fa3
Tx prefix hash: 54662dbcf4476044f063ce3eeb0f5f05e079e7f3f41a86ef8693ff4565cf8bc3
Tx public key: 008c764851743f78d921739f747ab233278a6c6ebc7a9fbf74b1d94c2f6d397d
| Timestamp: 1780694575 | Timestamp [UTC]: 2026-06-05 21:22:55 | Age [y:d:h:m:s]: 00:003:08:15:44 |
| Block: 5945 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2183 | RingCT/type: yes/0 |
| Extra: 01008c764851743f78d921739f747ab233278a6c6ebc7a9fbf74b1d94c2f6d397d020900000001e49593ff00 | ||
1 output(s) for total of 34.787729296811 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8cd68702632a20a3eb437a53c9927ae18011a4fa740f7748f63243a5fab697bd | 34.787729296811 | 7408 of 0 | <14> |
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": 6005,
"vin": [ {
"gen": {
"height": 5945
}
}
],
"vout": [ {
"amount": 34787729296811,
"target": {
"tagged_key": {
"key": "8cd68702632a20a3eb437a53c9927ae18011a4fa740f7748f63243a5fab697bd",
"view_tag": "14"
}
}
}
],
"extra": [ 1, 0, 140, 118, 72, 81, 116, 63, 120, 217, 33, 115, 159, 116, 122, 178, 51, 39, 138, 108, 110, 188, 122, 159, 191, 116, 177, 217, 76, 47, 109, 57, 125, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}