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: d906af25471ea3af9d12d32cc10c37ab0fba863a6078a2b3d7b07edf058014ef
Tx prefix hash: 661148ea5fc5e94827fa9c603fb274a08a3be340b92497337889cca5098d802a
Tx public key: 94ac1988e7979f0e89a31bb65e4744e7a4bef471266d1315b855289f308c14f7
| Timestamp: 1780686115 | Timestamp [UTC]: 2026-06-05 19:01:55 | Age [y:d:h:m:s]: 00:003:06:34:02 |
| Block: 5411 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2475 | RingCT/type: yes/0 |
| Extra: 0194ac1988e7979f0e89a31bb65e4744e7a4bef471266d1315b855289f308c14f7020900000001e49593ff00 | ||
1 output(s) for total of 34.823179524116 HMNY
| stealth address | amount | amount idx | tag |
| 00: b1c90b89f193bb7435a027a721f55c8d5a0514bdd139252c0c41d5f7848ca73c | 34.823179524116 | 6848 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": 5471,
"vin": [ {
"gen": {
"height": 5411
}
}
],
"vout": [ {
"amount": 34823179524116,
"target": {
"tagged_key": {
"key": "b1c90b89f193bb7435a027a721f55c8d5a0514bdd139252c0c41d5f7848ca73c",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 148, 172, 25, 136, 231, 151, 159, 14, 137, 163, 27, 182, 94, 71, 68, 231, 164, 190, 244, 113, 38, 109, 19, 21, 184, 85, 40, 159, 48, 140, 20, 247, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}