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: 47f087a916758b0bead1ca195bba192547bb74e4bdf6de764929bc31abe080c1
Tx prefix hash: d6f61df4ff04e6743a3d2d91bd3a5a2ed870549be682d3556df3c76ce7f4e250
Tx public key: aaf62837c287a01b50914a4603f49ddf5ac236173daaf0b352ffccd41d767877
| Timestamp: 1781004952 | Timestamp [UTC]: 2026-06-09 11:35:52 | Age [y:d:h:m:s]: 00:006:03:17:00 |
| Block: 8517 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 228 | RingCT/type: yes/0 |
| Extra: 01aaf62837c287a01b50914a4603f49ddf5ac236173daaf0b352ffccd41d767877020900000003e49593ff00 | ||
1 output(s) for total of 34.617488862787 HMNY
| stealth address | amount | amount idx | tag |
| 00: 735a60c3a83bc979165b32dc9b8615774ef0a0eefe56977ea1498c3dfe5205ca | 34.617488862787 | 10521 of 0 | <26> |
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": 8577,
"vin": [ {
"gen": {
"height": 8517
}
}
],
"vout": [ {
"amount": 34617488862787,
"target": {
"tagged_key": {
"key": "735a60c3a83bc979165b32dc9b8615774ef0a0eefe56977ea1498c3dfe5205ca",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 170, 246, 40, 55, 194, 135, 160, 27, 80, 145, 74, 70, 3, 244, 157, 223, 90, 194, 54, 23, 61, 170, 240, 179, 82, 255, 204, 212, 29, 118, 120, 119, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}