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: b9c6fe784b067cb5cab604891d8c137c07b2d6df989120d3b2601a66f7e34582
Tx prefix hash: 174b2b46aaf0ab265121bf4fd715b197c1e567e591e1b4a1d6755e70f8d1f9fc
Tx public key: 317c55b663e9ea9d2b58bb133b8e489972b853a67d472c3586776d4f08302c8d
| Timestamp: 1780847154 | Timestamp [UTC]: 2026-06-07 15:45:54 | Age [y:d:h:m:s]: 00:001:09:50:03 |
| Block: 7519 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 367 | RingCT/type: yes/0 |
| Extra: 01317c55b663e9ea9d2b58bb133b8e489972b853a67d472c3586776d4f08302c8d020900000002e49593ff00 | ||
1 output(s) for total of 34.683447247600 HMNY
| stealth address | amount | amount idx | tag |
| 00: 802eb429994e8f2163ffa5fe652d30ebf1e7b228b258105ff6730ef9fa752fa1 | 34.683447247600 | 9269 of 0 | <36> |
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": 7579,
"vin": [ {
"gen": {
"height": 7519
}
}
],
"vout": [ {
"amount": 34683447247600,
"target": {
"tagged_key": {
"key": "802eb429994e8f2163ffa5fe652d30ebf1e7b228b258105ff6730ef9fa752fa1",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 49, 124, 85, 182, 99, 233, 234, 157, 43, 88, 187, 19, 59, 142, 72, 153, 114, 184, 83, 166, 125, 71, 44, 53, 134, 119, 109, 79, 8, 48, 44, 141, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}