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: 975a178c18919f46198be8a1ef0f8c47cdf7d6cd4c1fe00217e1f2a2e33ccdf6
Tx prefix hash: 84cc38f054b116507ab0315d857292975194406edd184445540aed7af302df3e
Tx public key: ff07fbb518516e3e7ab4a277ed08969e48c80595903df5fde1df80c39465d2a1
| Timestamp: 1780693004 | Timestamp [UTC]: 2026-06-05 20:56:44 | Age [y:d:h:m:s]: 00:003:20:12:19 |
| Block: 5833 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2901 | RingCT/type: yes/0 |
| Extra: 01ff07fbb518516e3e7ab4a277ed08969e48c80595903df5fde1df80c39465d2a1020900000001e49593ff00 | ||
1 output(s) for total of 34.795161558448 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32550eaa73e4b351f3b60aedbd7e760b6d15adcf36295fd2d60d0232163259d1 | 34.795161558448 | 7290 of 0 | <85> |
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": 5893,
"vin": [ {
"gen": {
"height": 5833
}
}
],
"vout": [ {
"amount": 34795161558448,
"target": {
"tagged_key": {
"key": "32550eaa73e4b351f3b60aedbd7e760b6d15adcf36295fd2d60d0232163259d1",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 255, 7, 251, 181, 24, 81, 110, 62, 122, 180, 162, 119, 237, 8, 150, 158, 72, 200, 5, 149, 144, 61, 245, 253, 225, 223, 128, 195, 148, 101, 210, 161, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}