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: 5ab866054d4e2fd3be6934231eff8b1744ed6c47ea1579bdd5b5033028d6f498
Tx prefix hash: 43158c5580a18c3c2e3563142bf7cec6f1fd1d6dd58e3e0098a3f89d00172111
Tx public key: 6ed0bb6ad13500f72d49b7c5d7d6c733db29d62914adc10f5b836614a3c92db1
| Timestamp: 1779917359 | Timestamp [UTC]: 2026-05-27 21:29:19 | Age [y:d:h:m:s]: 00:018:10:50:16 |
| Block: 3328 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5417 | RingCT/type: yes/0 |
| Extra: 016ed0bb6ad13500f72d49b7c5d7d6c733db29d62914adc10f5b836614a3c92db102090000000226697be300 | ||
1 output(s) for total of 34.961807602198 HMNY
| stealth address | amount | amount idx | tag |
| 00: 37764cb2d6898c7ef2bc53afeb7ea89ea8dfa1d299b5cf7b3a20786a64f586fb | 34.961807602198 | 3998 of 0 | <f3> |
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": 3388,
"vin": [ {
"gen": {
"height": 3328
}
}
],
"vout": [ {
"amount": 34961807602198,
"target": {
"tagged_key": {
"key": "37764cb2d6898c7ef2bc53afeb7ea89ea8dfa1d299b5cf7b3a20786a64f586fb",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 110, 208, 187, 106, 209, 53, 0, 247, 45, 73, 183, 197, 215, 214, 199, 51, 219, 41, 214, 41, 20, 173, 193, 15, 91, 131, 102, 20, 163, 201, 45, 177, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}