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: 92fa140f94afe05f877952c35f7211016068eadabe47017bfb9d86ff60baa584
Tx prefix hash: 859e9a124c5b753b60bccc5a79b8103c6dc2acb7342463f6d062ffc6f0c84e27
Tx public key: 41f6d8fbc4a48b1f7619ab33e9e55221355c91d36969975a37368353f7dd125b
| Timestamp: 1780687292 | Timestamp [UTC]: 2026-06-05 19:21:32 | Age [y:d:h:m:s]: 00:003:06:14:25 |
| Block: 5473 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2413 | RingCT/type: yes/0 |
| Extra: 0141f6d8fbc4a48b1f7619ab33e9e55221355c91d36969975a37368353f7dd125b020900000001e49593ff00 | ||
1 output(s) for total of 34.819061727151 HMNY
| stealth address | amount | amount idx | tag |
| 00: c65086b497d56f7df49937e9052426c42e5b3b3a19dba4212c13bf5135eff50a | 34.819061727151 | 6912 of 0 | <f0> |
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": 5533,
"vin": [ {
"gen": {
"height": 5473
}
}
],
"vout": [ {
"amount": 34819061727151,
"target": {
"tagged_key": {
"key": "c65086b497d56f7df49937e9052426c42e5b3b3a19dba4212c13bf5135eff50a",
"view_tag": "f0"
}
}
}
],
"extra": [ 1, 65, 246, 216, 251, 196, 164, 139, 31, 118, 25, 171, 51, 233, 229, 82, 33, 53, 92, 145, 211, 105, 105, 151, 90, 55, 54, 131, 83, 247, 221, 18, 91, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}