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: f2d7ccc6b2237f9216c124ccf94656aefac690396e3d8f7c5858c02de7515a5c
Tx prefix hash: d78738fe2c2a8acc55ab3c945f977eb347a5088c21acdd844384be97206393ff
Tx public key: a8315901f461a995889155293d1ad9f4a828a923b96cdaad42a1701a0bbdc98c
| Timestamp: 1780986294 | Timestamp [UTC]: 2026-06-09 06:24:54 | Age [y:d:h:m:s]: 00:000:05:01:54 |
| Block: 8146 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 370 | RingCT/type: yes/0 |
| Extra: 01a8315901f461a995889155293d1ad9f4a828a923b96cdaad42a1701a0bbdc98c020900000001e49593ff00 | ||
1 output(s) for total of 34.641993802345 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0946813bc861449c6b7a51222269c58e2344f0cdf27abc058ce3c51c4b337c57 | 34.641993802345 | 10088 of 0 | <d1> |
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": 8206,
"vin": [ {
"gen": {
"height": 8146
}
}
],
"vout": [ {
"amount": 34641993802345,
"target": {
"tagged_key": {
"key": "0946813bc861449c6b7a51222269c58e2344f0cdf27abc058ce3c51c4b337c57",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 168, 49, 89, 1, 244, 97, 169, 149, 136, 145, 85, 41, 61, 26, 217, 244, 168, 40, 169, 35, 185, 108, 218, 173, 66, 161, 112, 26, 11, 189, 201, 140, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}