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: 91e84a61fe04c899ffa872498942e65253f71d5f54e92a64214b3dfcd87e9476
Tx prefix hash: 220f06a430f5befc8e17d61d818a41fab1ca23efcb3fc6fccccb06d8f3f8ec00
Tx public key: f451cd3b20629d4a722413f97f856d67620cd41425d07ba719a4125f45ab8397
| Timestamp: 1780820956 | Timestamp [UTC]: 2026-06-07 08:29:16 | Age [y:d:h:m:s]: 00:001:12:42:51 |
| Block: 7170 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 716 | RingCT/type: yes/0 |
| Extra: 01f451cd3b20629d4a722413f97f856d67620cd41425d07ba719a4125f45ab8397020900000001e49593ff00 | ||
1 output(s) for total of 34.706542501185 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97210754a16bf31ec5e066b4d36fdae88263d62dc618216b7a89d720de15c726 | 34.706542501185 | 8832 of 0 | <71> |
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": 7230,
"vin": [ {
"gen": {
"height": 7170
}
}
],
"vout": [ {
"amount": 34706542501185,
"target": {
"tagged_key": {
"key": "97210754a16bf31ec5e066b4d36fdae88263d62dc618216b7a89d720de15c726",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 244, 81, 205, 59, 32, 98, 157, 74, 114, 36, 19, 249, 127, 133, 109, 103, 98, 12, 212, 20, 37, 208, 123, 167, 25, 164, 18, 95, 69, 171, 131, 151, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}