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: 290e5370280cc9c219b0d0e923cc2436dd612f54a591a45e5e64a73b00257554
Tx prefix hash: 9f4d1b2317174fd2faf68fd63ad7a9ff6e5720cbbed6cb0b4bbed439e6a851e2
Tx public key: d103fccbba98ad872ccbc8029da723393af08cde5c777b7c247c0d5565be37d5
| Timestamp: 1780857898 | Timestamp [UTC]: 2026-06-07 18:44:58 | Age [y:d:h:m:s]: 00:001:04:33:55 |
| Block: 7590 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 296 | RingCT/type: yes/0 |
| Extra: 01d103fccbba98ad872ccbc8029da723393af08cde5c777b7c247c0d5565be37d5020900000001e49593ff00 | ||
1 output(s) for total of 34.678750667913 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c21b5dfd604cba67915e8f98853e9ddbd47ca4cb017647b3bdfc63ac5af0739 | 34.678750667913 | 9376 of 0 | <62> |
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": 7650,
"vin": [ {
"gen": {
"height": 7590
}
}
],
"vout": [ {
"amount": 34678750667913,
"target": {
"tagged_key": {
"key": "0c21b5dfd604cba67915e8f98853e9ddbd47ca4cb017647b3bdfc63ac5af0739",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 209, 3, 252, 203, 186, 152, 173, 135, 44, 203, 200, 2, 157, 167, 35, 57, 58, 240, 140, 222, 92, 119, 123, 124, 36, 124, 13, 85, 101, 190, 55, 213, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}