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: c0819a538baa02109cd034943fd1e0b87c2ea2aefb904862509d9155a4bb6a6e
Tx prefix hash: 4a0d6fd383a270456c0d7ab6cf0ead19d54b7f62a55fdcf9eb97be6a8fc3f1de
Tx public key: 814493e64cfa8e4ad48b84c746be24510c863109ca106fa92f3981c1a2e001c6
| Timestamp: 1780798047 | Timestamp [UTC]: 2026-06-07 02:07:27 | Age [y:d:h:m:s]: 00:006:08:54:49 |
| Block: 6789 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1956 | RingCT/type: yes/0 |
| Extra: 01814493e64cfa8e4ad48b84c746be24510c863109ca106fa92f3981c1a2e001c6020900000002e49593ff00 | ||
1 output(s) for total of 34.731772930115 HMNY
| stealth address | amount | amount idx | tag |
| 00: b2541163e429666325dabeeb55f2a52439e75540c731bfbeded10a15815645cb | 34.731772930115 | 8383 of 0 | <6d> |
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": 6849,
"vin": [ {
"gen": {
"height": 6789
}
}
],
"vout": [ {
"amount": 34731772930115,
"target": {
"tagged_key": {
"key": "b2541163e429666325dabeeb55f2a52439e75540c731bfbeded10a15815645cb",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 129, 68, 147, 230, 76, 250, 142, 74, 212, 139, 132, 199, 70, 190, 36, 81, 12, 134, 49, 9, 202, 16, 111, 169, 47, 57, 129, 193, 162, 224, 1, 198, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}