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: 435730f88ec6e3e9805c67b4a39ba3fc899f0729343006fa89b1a7113d1f4212
Tx prefix hash: 6cb2fb1d97b36109b85e6af7c8a5718e46395d7833f9419055e71056c86a3aa8
Tx public key: f1ee283ac6e03ecd60b96f5fee00b66fbd7475f538c23d98d263db7344a658bd
| Timestamp: 1780036873 | Timestamp [UTC]: 2026-05-29 06:41:13 | Age [y:d:h:m:s]: 00:010:20:08:35 |
| Block: 4246 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3663 | RingCT/type: yes/0 |
| Extra: 01f1ee283ac6e03ecd60b96f5fee00b66fbd7475f538c23d98d263db7344a658bd02090000000126697be300 | ||
1 output(s) for total of 34.903259667075 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56e115b93444c9b0c23d0e4fa1c62b775c15e035f4e0333bf2b4d72826838eaa | 34.903259667075 | 5299 of 0 | <97> |
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": 4306,
"vin": [ {
"gen": {
"height": 4246
}
}
],
"vout": [ {
"amount": 34903259667075,
"target": {
"tagged_key": {
"key": "56e115b93444c9b0c23d0e4fa1c62b775c15e035f4e0333bf2b4d72826838eaa",
"view_tag": "97"
}
}
}
],
"extra": [ 1, 241, 238, 40, 58, 198, 224, 62, 205, 96, 185, 111, 95, 238, 0, 182, 111, 189, 116, 117, 245, 56, 194, 61, 152, 210, 99, 219, 115, 68, 166, 88, 189, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}