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: 1bb940caeb610f3d84d8d8794ce6ad1e69e891fa2dc3e609fb4b5ab2de52c545
Tx prefix hash: 9f115fb9174e107213040d1bce4bfda79e5f42c361b035c2b15833c1583a957d
Tx public key: e7339bf742f87340c67f287d78e14994398099001a1d3b7e8c765c08ca5a8cd0
| Timestamp: 1779454476 | Timestamp [UTC]: 2026-05-22 12:54:36 | Age [y:d:h:m:s]: 00:017:12:41:21 |
| Block: 366 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7520 | RingCT/type: yes/0 |
| Extra: 01e7339bf742f87340c67f287d78e14994398099001a1d3b7e8c765c08ca5a8cd002090000000293369e7d00 | ||
1 output(s) for total of 35.159885854663 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc66c9b2b01e99494a1c1d45f841f0cac808900f9e8a5447341f3825681a81a8 | 35.159885854663 | 362 of 0 | <42> |
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": 426,
"vin": [ {
"gen": {
"height": 366
}
}
],
"vout": [ {
"amount": 35159885854663,
"target": {
"tagged_key": {
"key": "fc66c9b2b01e99494a1c1d45f841f0cac808900f9e8a5447341f3825681a81a8",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 231, 51, 155, 247, 66, 248, 115, 64, 198, 127, 40, 125, 120, 225, 73, 148, 57, 128, 153, 0, 26, 29, 59, 126, 140, 118, 92, 8, 202, 90, 140, 208, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}