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: 51d8447633f7d58eecab9b79c8e15450f426d74ee7456dde70b9016c620172f1
Tx prefix hash: f8ed788acdcd63f9c985ae86595cb4086187698cfab70b0e1d3cf386002b457e
Tx public key: 44f4b83de81e19660f25dfd71bbaae54024b10aa1a670c30bcc2b7712de086e2
| Timestamp: 1780685140 | Timestamp [UTC]: 2026-06-05 18:45:40 | Age [y:d:h:m:s]: 00:003:06:50:17 |
| Block: 5373 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2513 | RingCT/type: yes/0 |
| Extra: 0144f4b83de81e19660f25dfd71bbaae54024b10aa1a670c30bcc2b7712de086e2020900000001e49593ff00 | ||
1 output(s) for total of 34.825703575859 HMNY
| stealth address | amount | amount idx | tag |
| 00: 481b7964fbf100fe0f1113d365f9fa40bfe46b9516969dbeb3bde259dea364fd | 34.825703575859 | 6808 of 0 | <f5> |
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": 5433,
"vin": [ {
"gen": {
"height": 5373
}
}
],
"vout": [ {
"amount": 34825703575859,
"target": {
"tagged_key": {
"key": "481b7964fbf100fe0f1113d365f9fa40bfe46b9516969dbeb3bde259dea364fd",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 68, 244, 184, 61, 232, 30, 25, 102, 15, 37, 223, 215, 27, 186, 174, 84, 2, 75, 16, 170, 26, 103, 12, 48, 188, 194, 183, 113, 45, 224, 134, 226, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}