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: f976eb674f5380c314a1bb330272d92d1adb1fe3be6dea63d811824af447d59f
Tx prefix hash: 068611b243efac7761c563ed028b5d5611d50d6a8d06903c419a2d8229a69fc7
Tx public key: 6c023678e1a6a33b5b3cd5737e4ee1fa54cf9774b70dfd60522c1beb44076f12
| Timestamp: 1779900173 | Timestamp [UTC]: 2026-05-27 16:42:53 | Age [y:d:h:m:s]: 00:012:08:03:54 |
| Block: 3134 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4752 | RingCT/type: yes/0 |
| Extra: 016c023678e1a6a33b5b3cd5737e4ee1fa54cf9774b70dfd60522c1beb44076f1202090000000326697be300 | ||
1 output(s) for total of 34.974746773353 HMNY
| stealth address | amount | amount idx | tag |
| 00: f85824b27c63011a7d9f9f032415a6bd384b644c90204fb037a8f36b2b07702a | 34.974746773353 | 3746 of 0 | <4d> |
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": 3194,
"vin": [ {
"gen": {
"height": 3134
}
}
],
"vout": [ {
"amount": 34974746773353,
"target": {
"tagged_key": {
"key": "f85824b27c63011a7d9f9f032415a6bd384b644c90204fb037a8f36b2b07702a",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 108, 2, 54, 120, 225, 166, 163, 59, 91, 60, 213, 115, 126, 78, 225, 250, 84, 207, 151, 116, 183, 13, 253, 96, 82, 44, 27, 235, 68, 7, 111, 18, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}