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: 32f91877e23985a41db36215e109350d7a99ddb84cc7dcadf641caebbd79733c
Tx prefix hash: 9e3cc2a1f3ec3d60d342f7da0f728e356eb625bbee94b326d3ed092f49ba57a8
Tx public key: ed70cde4a5903578450c0ddf72bf3cda42b9f87b3b83896f41e2a5c1be246998
| Timestamp: 1779639671 | Timestamp [UTC]: 2026-05-24 16:21:11 | Age [y:d:h:m:s]: 00:019:18:41:05 |
| Block: 1259 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7486 | RingCT/type: yes/0 |
| Extra: 01ed70cde4a5903578450c0ddf72bf3cda42b9f87b3b83896f41e2a5c1be246998020900000001ba6d17be00 | ||
1 output(s) for total of 35.100050260850 HMNY
| stealth address | amount | amount idx | tag |
| 00: 05c8d576f2f8600d213467385492fcdc844700af28095ca4074b26f59bef9731 | 35.100050260850 | 1405 of 0 | <b9> |
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": 1319,
"vin": [ {
"gen": {
"height": 1259
}
}
],
"vout": [ {
"amount": 35100050260850,
"target": {
"tagged_key": {
"key": "05c8d576f2f8600d213467385492fcdc844700af28095ca4074b26f59bef9731",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 237, 112, 205, 228, 165, 144, 53, 120, 69, 12, 13, 223, 114, 191, 60, 218, 66, 185, 248, 123, 59, 131, 137, 111, 65, 226, 165, 193, 190, 36, 105, 152, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}