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: 436a882387c023bf05c240e7474ebf66129d5f031fb34e2ce6c1c0e5815f4e54
Tx prefix hash: 6acecff159ecedc22cebd5bafeb6d39e470d39b32ee2852ae850098bf208196b
Tx public key: d806947665053456c1432955b842f12f1dd54a6beb9f16a2e0e5db0a2dea45ff
| Timestamp: 1780807398 | Timestamp [UTC]: 2026-06-07 04:43:18 | Age [y:d:h:m:s]: 00:001:20:03:29 |
| Block: 6963 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 923 | RingCT/type: yes/0 |
| Extra: 01d806947665053456c1432955b842f12f1dd54a6beb9f16a2e0e5db0a2dea45ff020900000001e49593ff00 | ||
1 output(s) for total of 34.726075297320 HMNY
| stealth address | amount | amount idx | tag |
| 00: 06b0bab1aa6ac73c74e93ba9381daa7b3220287e51119ac7be15a8f749b5583b | 34.726075297320 | 8587 of 0 | <ff> |
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": 7023,
"vin": [ {
"gen": {
"height": 6963
}
}
],
"vout": [ {
"amount": 34726075297320,
"target": {
"tagged_key": {
"key": "06b0bab1aa6ac73c74e93ba9381daa7b3220287e51119ac7be15a8f749b5583b",
"view_tag": "ff"
}
}
}
],
"extra": [ 1, 216, 6, 148, 118, 101, 5, 52, 86, 193, 67, 41, 85, 184, 66, 241, 47, 29, 213, 74, 107, 235, 159, 22, 162, 224, 229, 219, 10, 45, 234, 69, 255, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}