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: 16ab130a7079a2a44b89c60b5dabd843e9f4ced2399b851667609317b360b800
Tx prefix hash: 50a604b4b82edc2843ce90a1d1906073bbd1da39a514e410f574cbc29f1b6e79
Tx public key: 055995cf14519a3bd98556480dcfbefa8ebc4e4296ac032a1d58d7ebd10fdcff
| Timestamp: 1779918451 | Timestamp [UTC]: 2026-05-27 21:47:31 | Age [y:d:h:m:s]: 00:012:02:59:16 |
| Block: 3338 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4548 | RingCT/type: yes/0 |
| Extra: 01055995cf14519a3bd98556480dcfbefa8ebc4e4296ac032a1d58d7ebd10fdcff02090000000226697be300 | ||
1 output(s) for total of 34.961140764363 HMNY
| stealth address | amount | amount idx | tag |
| 00: b98558701ec0a9fe73f0a18e8d7f3f692517825ddb217d1dbda2b7307b96e24c | 34.961140764363 | 4011 of 0 | <f4> |
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": 3398,
"vin": [ {
"gen": {
"height": 3338
}
}
],
"vout": [ {
"amount": 34961140764363,
"target": {
"tagged_key": {
"key": "b98558701ec0a9fe73f0a18e8d7f3f692517825ddb217d1dbda2b7307b96e24c",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 5, 89, 149, 207, 20, 81, 154, 59, 217, 133, 86, 72, 13, 207, 190, 250, 142, 188, 78, 66, 150, 172, 3, 42, 29, 88, 215, 235, 209, 15, 220, 255, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}