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: 693560468c3c1ab4b78ff67f484a83d2469bee51ad0e50bd386720399fddfcfa
Tx prefix hash: aeb78aebb51f9008bb680d7f733f1e034b68745a80ba7314dc8b4e8912ade0db
Tx public key: a34e2f2d4422af9b70e07b23652c48a0e4709d2ec1ae45bf2d3da6dba99864f8
| Timestamp: 1781018726 | Timestamp [UTC]: 2026-06-09 15:25:26 | Age [y:d:h:m:s]: 00:006:01:17:48 |
| Block: 8663 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 82 | RingCT/type: yes/0 |
| Extra: 01a34e2f2d4422af9b70e07b23652c48a0e4709d2ec1ae45bf2d3da6dba99864f8020900000001e49593ff00 | ||
1 output(s) for total of 34.607850163188 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16646a716834b6109de4dd31dece2dca602703b30fca77e4a52d6ab4b204fdaf | 34.607850163188 | 10711 of 0 | <69> |
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": 8723,
"vin": [ {
"gen": {
"height": 8663
}
}
],
"vout": [ {
"amount": 34607850163188,
"target": {
"tagged_key": {
"key": "16646a716834b6109de4dd31dece2dca602703b30fca77e4a52d6ab4b204fdaf",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 163, 78, 47, 45, 68, 34, 175, 155, 112, 224, 123, 35, 101, 44, 72, 160, 228, 112, 157, 46, 193, 174, 69, 191, 45, 61, 166, 219, 169, 152, 100, 248, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}