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: d954eea5139a76603e784f5380d03d5af607aa5c09ccc00a5021ea1601edc4f3
Tx prefix hash: 5b2472b34dba0875f6be8b6d6e2f0b2cb6e569223f0f46c30f93b1bf24f24811
Tx public key: b9e6c5c0ce72d24f32c20b382a9f57eeb339c149284913a532472fe8a3a29bb1
| Timestamp: 1779450362 | Timestamp [UTC]: 2026-05-22 11:46:02 | Age [y:d:h:m:s]: 00:017:10:38:47 |
| Block: 316 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7570 | RingCT/type: yes/0 |
| Extra: 01b9e6c5c0ce72d24f32c20b382a9f57eeb339c149284913a532472fe8a3a29bb10209000000034438f87f00 | ||
1 output(s) for total of 35.163239125766 HMNY
| stealth address | amount | amount idx | tag |
| 00: d91cd59e0a919cf942411917fd2ea34cf2e496bc8311f2eec1b01fd0fb300d9b | 35.163239125766 | 312 of 0 | <74> |
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": 376,
"vin": [ {
"gen": {
"height": 316
}
}
],
"vout": [ {
"amount": 35163239125766,
"target": {
"tagged_key": {
"key": "d91cd59e0a919cf942411917fd2ea34cf2e496bc8311f2eec1b01fd0fb300d9b",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 185, 230, 197, 192, 206, 114, 210, 79, 50, 194, 11, 56, 42, 159, 87, 238, 179, 57, 193, 73, 40, 73, 19, 165, 50, 71, 47, 232, 163, 162, 155, 177, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}