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: ceb147157b9e0f2efe36546c07bb565e61c1ca1421e19a81c15f46083bc5824f
Tx prefix hash: f97c5721addebf47efe18d4c75fd431045299aab614e7ce19e07f4ee2ad785fa
Tx public key: 51a68757d46fe9a35f992c2111674e94f1e67d56baf941a86a50713e882128e7
| Timestamp: 1779912720 | Timestamp [UTC]: 2026-05-27 20:12:00 | Age [y:d:h:m:s]: 00:012:06:37:48 |
| Block: 3263 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4657 | RingCT/type: yes/0 |
| Extra: 0151a68757d46fe9a35f992c2111674e94f1e67d56baf941a86a50713e882128e702090000000526697be300 | ||
1 output(s) for total of 34.966142358169 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c193c78c419a545a0c3bba1345af95ffe5a73c041fe9ba8a5f3d1c36bf5f3f5 | 34.966142358169 | 3917 of 0 | <70> |
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": 3323,
"vin": [ {
"gen": {
"height": 3263
}
}
],
"vout": [ {
"amount": 34966142358169,
"target": {
"tagged_key": {
"key": "9c193c78c419a545a0c3bba1345af95ffe5a73c041fe9ba8a5f3d1c36bf5f3f5",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 81, 166, 135, 87, 212, 111, 233, 163, 95, 153, 44, 33, 17, 103, 78, 148, 241, 230, 125, 86, 186, 249, 65, 168, 106, 80, 113, 62, 136, 33, 40, 231, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}