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: 9417e02fda37ac07e83c74f7a31e3a3b6e91204dc194e518d464d8c8bff5b9de
Tx prefix hash: 774d6823d9f4de93228c600035c896d0497a68f9cc6510e3ac7c74681da6e2f0
Tx public key: 52034bc2a11d1c62c1f71b5399635151c63a32131d61fa35d45396ddeadafa84
| Timestamp: 1779457567 | Timestamp [UTC]: 2026-05-22 13:46:07 | Age [y:d:h:m:s]: 00:017:11:49:50 |
| Block: 406 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7480 | RingCT/type: yes/0 |
| Extra: 0152034bc2a11d1c62c1f71b5399635151c63a32131d61fa35d45396ddeadafa8402090000000293369e7d00 | ||
1 output(s) for total of 35.157203468023 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf631ca826b0a6f257860eed1dd6fa690b41022803c5447a853b975ead222c37 | 35.157203468023 | 408 of 0 | <60> |
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": 466,
"vin": [ {
"gen": {
"height": 406
}
}
],
"vout": [ {
"amount": 35157203468023,
"target": {
"tagged_key": {
"key": "bf631ca826b0a6f257860eed1dd6fa690b41022803c5447a853b975ead222c37",
"view_tag": "60"
}
}
}
],
"extra": [ 1, 82, 3, 75, 194, 161, 29, 28, 98, 193, 247, 27, 83, 153, 99, 81, 81, 198, 58, 50, 19, 29, 97, 250, 53, 212, 83, 150, 221, 234, 218, 250, 132, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}