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: 878d075c4bbc5e7a8678453355dc62491c6db02d1bb4d39065c7e1c31c7ea3d5
Tx prefix hash: ae07a82b2460e2aa1fd143403cd8530f7c10101461778419a8667737596cfedb
Tx public key: 48c464584b39164c6eb607868f391e08bf4ba7fcb81105771cb0b6063ca4bbd9
| Timestamp: 1779976889 | Timestamp [UTC]: 2026-05-28 14:01:29 | Age [y:d:h:m:s]: 00:011:09:17:24 |
| Block: 3889 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3997 | RingCT/type: yes/0 |
| Extra: 0148c464584b39164c6eb607868f391e08bf4ba7fcb81105771cb0b6063ca4bbd902090000000426697be300 | ||
1 output(s) for total of 34.924417650477 HMNY
| stealth address | amount | amount idx | tag |
| 00: 24e4e3b69210d85f6b947737c947af675892525b264f2f3b4e8813f13471d057 | 34.924417650477 | 4764 of 0 | <5b> |
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": 3949,
"vin": [ {
"gen": {
"height": 3889
}
}
],
"vout": [ {
"amount": 34924417650477,
"target": {
"tagged_key": {
"key": "24e4e3b69210d85f6b947737c947af675892525b264f2f3b4e8813f13471d057",
"view_tag": "5b"
}
}
}
],
"extra": [ 1, 72, 196, 100, 88, 75, 57, 22, 76, 110, 182, 7, 134, 143, 57, 30, 8, 191, 75, 167, 252, 184, 17, 5, 119, 28, 176, 182, 6, 60, 164, 187, 217, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}