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: 1bbf5b23146fa11de4457cfe516818e0be79ad761ce6067c55f7ef31a8409aaa
Tx prefix hash: e9aeb9be4634e80a40a60abd538ee1978aae088462c71fa2752ae3e943403a51
Tx public key: 6e98b99ae645e3796ef02eab6b8a23015677d10cb5bf70130dadb7e6f64dcf8e
| Timestamp: 1779633766 | Timestamp [UTC]: 2026-05-24 14:42:46 | Age [y:d:h:m:s]: 00:015:08:36:07 |
| Block: 1004 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6882 | RingCT/type: yes/0 |
| Extra: 016e98b99ae645e3796ef02eab6b8a23015677d10cb5bf70130dadb7e6f64dcf8e020900000002ba6d17be00 | ||
1 output(s) for total of 35.117126177822 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8bbd28aed645a9e297a5b704833b330a42d8758f21acb48f6eda435fff7c5a47 | 35.117126177822 | 1140 of 0 | <40> |
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": 1064,
"vin": [ {
"gen": {
"height": 1004
}
}
],
"vout": [ {
"amount": 35117126177822,
"target": {
"tagged_key": {
"key": "8bbd28aed645a9e297a5b704833b330a42d8758f21acb48f6eda435fff7c5a47",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 110, 152, 185, 154, 230, 69, 227, 121, 110, 240, 46, 171, 107, 138, 35, 1, 86, 119, 209, 12, 181, 191, 112, 19, 13, 173, 183, 230, 246, 77, 207, 142, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}