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: f1656719112b0a801f1c6f3faa0be28b45671b3602d6a41aa0964ba948f73fd8
Tx prefix hash: 1891ffe308015cf7d015ce12521230f92af903d2a1d0bdc49f94f9fa344dc37c
Tx public key: f87c9dc44b78ab6fd5be0232570f6ebb4d7a36184643fbf2de1149070227ad8d
| Timestamp: 1779868954 | Timestamp [UTC]: 2026-05-27 08:02:34 | Age [y:d:h:m:s]: 00:012:17:33:23 |
| Block: 2778 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5108 | RingCT/type: yes/0 |
| Extra: 01f87c9dc44b78ab6fd5be0232570f6ebb4d7a36184643fbf2de1149070227ad8d02090000000226697be300 | ||
1 output(s) for total of 34.998503277238 HMNY
| stealth address | amount | amount idx | tag |
| 00: 01bfb74e396453e650cb9ac400c485faa23f033f44cf29b9153d0fe25eb14440 | 34.998503277238 | 3286 of 0 | <83> |
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": 2838,
"vin": [ {
"gen": {
"height": 2778
}
}
],
"vout": [ {
"amount": 34998503277238,
"target": {
"tagged_key": {
"key": "01bfb74e396453e650cb9ac400c485faa23f033f44cf29b9153d0fe25eb14440",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 248, 124, 157, 196, 75, 120, 171, 111, 213, 190, 2, 50, 87, 15, 110, 187, 77, 122, 54, 24, 70, 67, 251, 242, 222, 17, 73, 7, 2, 39, 173, 141, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}