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: d4da48f9c729e05dfbf17378dd9dae01b836c15876d8e7b71c84d068dd250ecd
Tx prefix hash: 998b67f99e7db7d1f757acfb4eaa6016e6c5144eca9f41a6611e490ad162d35e
Tx public key: d3b7d90a45d2f7dc87245ed0719b023360d40837a4cfaa24d05367ec267f729e
| Timestamp: 1779874301 | Timestamp [UTC]: 2026-05-27 09:31:41 | Age [y:d:h:m:s]: 00:012:17:18:07 |
| Block: 2860 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5060 | RingCT/type: yes/0 |
| Extra: 01d3b7d90a45d2f7dc87245ed0719b023360d40837a4cfaa24d05367ec267f729e02090000000326697be300 | ||
1 output(s) for total of 34.993029843574 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f5bc8227a358ff2999d3cfcab84576e285c318f0a4e77fecb81407b4aa0bfb9 | 34.993029843574 | 3386 of 0 | <b4> |
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": 2920,
"vin": [ {
"gen": {
"height": 2860
}
}
],
"vout": [ {
"amount": 34993029843574,
"target": {
"tagged_key": {
"key": "2f5bc8227a358ff2999d3cfcab84576e285c318f0a4e77fecb81407b4aa0bfb9",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 211, 183, 217, 10, 69, 210, 247, 220, 135, 36, 94, 208, 113, 155, 2, 51, 96, 212, 8, 55, 164, 207, 170, 36, 208, 83, 103, 236, 38, 127, 114, 158, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}