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: 00ac83653b5030eb8508d632d5f56388fd4da85cc3520ebbd05b85ad07a22c62
Tx prefix hash: bef255db2bab4058f11a1fbb755d83d537cfb179df8674551c062031a7f6c15a
Tx public key: 6bcbc1053b374f17ed1ab1f902bc7c8e6762d5a669371013dc8e00da66a61904
| Timestamp: 1779433938 | Timestamp [UTC]: 2026-05-22 07:12:18 | Age [y:d:h:m:s]: 00:017:19:37:30 |
| Block: 70 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7850 | RingCT/type: yes/0 |
| Extra: 016bcbc1053b374f17ed1ab1f902bc7c8e6762d5a669371013dc8e00da66a61904020900000001a662ed0300 | ||
1 output(s) for total of 35.179741877604 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1db100d35ea5a62e97cf3a6119684ec33c1098f65d115f4ddc457e2b384537aa | 35.179741877604 | 66 of 0 | <ef> |
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": 130,
"vin": [ {
"gen": {
"height": 70
}
}
],
"vout": [ {
"amount": 35179741877604,
"target": {
"tagged_key": {
"key": "1db100d35ea5a62e97cf3a6119684ec33c1098f65d115f4ddc457e2b384537aa",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 107, 203, 193, 5, 59, 55, 79, 23, 237, 26, 177, 249, 2, 188, 124, 142, 103, 98, 213, 166, 105, 55, 16, 19, 220, 142, 0, 218, 102, 166, 25, 4, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}