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: 91e4bbc8a862a0d5457137c316c62c1b8d2b937f3a5d461401a4d9e49d9c6200
Tx prefix hash: 74f87dcf41417fedc36962b205729ab36fb466bd5e9c378eaf1bf0e504c0923e
Tx public key: 9a14430576b20b04a5a14db33ed82d08a6a4e2858a31d8906dd608b7aa6a1962
| Timestamp: 1779850779 | Timestamp [UTC]: 2026-05-27 02:59:39 | Age [y:d:h:m:s]: 00:012:20:19:14 |
| Block: 2524 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5362 | RingCT/type: yes/0 |
| Extra: 019a14430576b20b04a5a14db33ed82d08a6a4e2858a31d8906dd608b7aa6a196202090000000126697be300 | ||
1 output(s) for total of 35.015463005525 HMNY
| stealth address | amount | amount idx | tag |
| 00: bd20f8d143e6fdfa6aca362ed55dbaba1fa21401d9aa80bb8733c0ebc8ad388f | 35.015463005525 | 2972 of 0 | <85> |
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": 2584,
"vin": [ {
"gen": {
"height": 2524
}
}
],
"vout": [ {
"amount": 35015463005525,
"target": {
"tagged_key": {
"key": "bd20f8d143e6fdfa6aca362ed55dbaba1fa21401d9aa80bb8733c0ebc8ad388f",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 154, 20, 67, 5, 118, 178, 11, 4, 165, 161, 77, 179, 62, 216, 45, 8, 166, 164, 226, 133, 138, 49, 216, 144, 109, 214, 8, 183, 170, 106, 25, 98, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}