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: d9082c5ccf2f227e6d6e26e6ca5cb6c8e3d9a9acb05b61d8c21b8e4dc56255f6
Tx prefix hash: 9951b0562b5f2940523183987a93580de6ddbb0568449c2f953b8ab3ae1dc4e0
Tx public key: c8c9e9628e631397bffa91fa8e8f55a76efaa16a4bfc5250adf1c2d04e04815c
| Timestamp: 1780902457 | Timestamp [UTC]: 2026-06-08 07:07:37 | Age [y:d:h:m:s]: 00:000:16:11:16 |
| Block: 7833 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 53 | RingCT/type: yes/0 |
| Extra: 01c8c9e9628e631397bffa91fa8e8f55a76efaa16a4bfc5250adf1c2d04e04815c0209000000014a728a4c00 | ||
1 output(s) for total of 34.662681271199 HMNY
| stealth address | amount | amount idx | tag |
| 00: f0bb9ef2c50fc84c6494901c464a2fdaf97120dea0ef070e1c6e2bc534078174 | 34.662681271199 | 9709 of 0 | <f4> |
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": 7893,
"vin": [ {
"gen": {
"height": 7833
}
}
],
"vout": [ {
"amount": 34662681271199,
"target": {
"tagged_key": {
"key": "f0bb9ef2c50fc84c6494901c464a2fdaf97120dea0ef070e1c6e2bc534078174",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 200, 201, 233, 98, 142, 99, 19, 151, 191, 250, 145, 250, 142, 143, 85, 167, 110, 250, 161, 106, 75, 252, 82, 80, 173, 241, 194, 208, 78, 4, 129, 92, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}