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: 36d93763879d066ac8768a41be8a2be3b36413c999f99d261d8ea082c99d0773
Tx prefix hash: cf70db1cdb5c9ea24aa413ccb5de7ae899e17b7fba8cccf19a2fe1406eda6ca0
Tx public key: 1397b7a5f9bf62c6a62d28e170b4c32856add9a706f6ae1f5b5ab037d5aa99f9
| Timestamp: 1780981877 | Timestamp [UTC]: 2026-06-09 05:11:17 | Age [y:d:h:m:s]: 00:000:07:26:28 |
| Block: 8051 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 523 | RingCT/type: yes/0 |
| Extra: 011397b7a5f9bf62c6a62d28e170b4c32856add9a706f6ae1f5b5ab037d5aa99f9020900000001e49593ff00 | ||
1 output(s) for total of 34.648271441217 HMNY
| stealth address | amount | amount idx | tag |
| 00: d71520c6a141727d3e227b201487eb7e169be355cabccef6db21c4d885e91a23 | 34.648271441217 | 9979 of 0 | <0b> |
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": 8111,
"vin": [ {
"gen": {
"height": 8051
}
}
],
"vout": [ {
"amount": 34648271441217,
"target": {
"tagged_key": {
"key": "d71520c6a141727d3e227b201487eb7e169be355cabccef6db21c4d885e91a23",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 19, 151, 183, 165, 249, 191, 98, 198, 166, 45, 40, 225, 112, 180, 195, 40, 86, 173, 217, 167, 6, 246, 174, 31, 91, 90, 176, 55, 213, 170, 153, 249, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}