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: 503415eb4a95284ae1c339fadfb7bcdbdc90ddc3fbf2f61080c406a4a3cb7cd6
Tx prefix hash: e80aebb8621711aa863d63d067fdbe9992ce52b7e1047be1b7864e623e352860
Tx public key: a33ba7937465c2d58ae7c5ff683c56059bab546134d0760d9ed392b2d687d9cd
| Timestamp: 1780683422 | Timestamp [UTC]: 2026-06-05 18:17:02 | Age [y:d:h:m:s]: 00:007:16:45:14 |
| Block: 5323 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3422 | RingCT/type: yes/0 |
| Extra: 01a33ba7937465c2d58ae7c5ff683c56059bab546134d0760d9ed392b2d687d9cd020900000001e49593ff00 | ||
1 output(s) for total of 34.829024975306 HMNY
| stealth address | amount | amount idx | tag |
| 00: 24e3cade8ef683b3de3ba818c67128e1bb74c8b0bb5ce186b665d96a0f33448b | 34.829024975306 | 6752 of 0 | <c1> |
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": 5383,
"vin": [ {
"gen": {
"height": 5323
}
}
],
"vout": [ {
"amount": 34829024975306,
"target": {
"tagged_key": {
"key": "24e3cade8ef683b3de3ba818c67128e1bb74c8b0bb5ce186b665d96a0f33448b",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 163, 59, 167, 147, 116, 101, 194, 213, 138, 231, 197, 255, 104, 60, 86, 5, 155, 171, 84, 97, 52, 208, 118, 13, 158, 211, 146, 178, 214, 135, 217, 205, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}