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: dd4fdde05c34f4dc48b093ad00cf972113ea649d588544952f4644d553823752
Tx prefix hash: c80a9011e4fcf0f841eaec2bf2ff320dd31b507a9bf1a4aeecbe90e9189d632d
Tx public key: 327fbb6e017998ac78d87fb91eea9bae49ed10a825a2e9fa98e398ac6eb8dc39
| Timestamp: 1780986330 | Timestamp [UTC]: 2026-06-09 06:25:30 | Age [y:d:h:m:s]: 00:000:05:01:18 |
| Block: 8147 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 369 | RingCT/type: yes/0 |
| Extra: 01327fbb6e017998ac78d87fb91eea9bae49ed10a825a2e9fa98e398ac6eb8dc39020900000001e49593ff00 | ||
1 output(s) for total of 34.641927727985 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2733f21c292f681a77b7fc5ed3751455999d151d2587385a166c57703dd31bb | 34.641927727985 | 10089 of 0 | <2a> |
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": 8207,
"vin": [ {
"gen": {
"height": 8147
}
}
],
"vout": [ {
"amount": 34641927727985,
"target": {
"tagged_key": {
"key": "c2733f21c292f681a77b7fc5ed3751455999d151d2587385a166c57703dd31bb",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 50, 127, 187, 110, 1, 121, 152, 172, 120, 216, 127, 185, 30, 234, 155, 174, 73, 237, 16, 168, 37, 162, 233, 250, 152, 227, 152, 172, 110, 184, 220, 57, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}