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: 3bffda0537bd42c4128269b716a4e3a503ed01ebad1977c879f758ba4ed59d3b
Tx prefix hash: 2f8fb692eb1be01521c4b486a51d02574a49cd2f8d61db87cf603ab395e1b3ec
Tx public key: 8471f1e6b072ec09c45e82db9c776608c6228d5ece16c5a6a632b84d1ba65282
| Timestamp: 1781014006 | Timestamp [UTC]: 2026-06-09 14:06:46 | Age [y:d:h:m:s]: 00:006:05:15:23 |
| Block: 8614 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 131 | RingCT/type: yes/0 |
| Extra: 018471f1e6b072ec09c45e82db9c776608c6228d5ece16c5a6a632b84d1ba65282020900000001e49593ff00 | ||
1 output(s) for total of 34.611084769973 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c091ca2b2bfe6761f4d979881a6fce66001220bcbf30dd864cae26c3593efd3 | 34.611084769973 | 10646 of 0 | <4c> |
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": 8674,
"vin": [ {
"gen": {
"height": 8614
}
}
],
"vout": [ {
"amount": 34611084769973,
"target": {
"tagged_key": {
"key": "9c091ca2b2bfe6761f4d979881a6fce66001220bcbf30dd864cae26c3593efd3",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 132, 113, 241, 230, 176, 114, 236, 9, 196, 94, 130, 219, 156, 119, 102, 8, 198, 34, 141, 94, 206, 22, 197, 166, 166, 50, 184, 77, 27, 166, 82, 130, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}