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: e850674f2b8e4bf802af1db06062d448d7501dbb213555c7f49b5d79f4ced5fc
Tx prefix hash: 31f03228e5eaa625ceb5e3dd8c3eac0f2c1ab915ede3ab8bf05daa4f9750d472
Tx public key: 2c1f9d1794072b416def1de59137ab6edd79ee91966a65858aa732d1e412704a
| Timestamp: 1780696848 | Timestamp [UTC]: 2026-06-05 22:00:48 | Age [y:d:h:m:s]: 00:003:01:18:05 |
| Block: 6001 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1885 | RingCT/type: yes/0 |
| Extra: 012c1f9d1794072b416def1de59137ab6edd79ee91966a65858aa732d1e412704a020900000002e49593ff00 | ||
1 output(s) for total of 34.784013761339 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3aa705dada9c70d608593373ccff2e8d7a4845cf9e800bf90b2b96f48f501741 | 34.784013761339 | 7468 of 0 | <67> |
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": 6061,
"vin": [ {
"gen": {
"height": 6001
}
}
],
"vout": [ {
"amount": 34784013761339,
"target": {
"tagged_key": {
"key": "3aa705dada9c70d608593373ccff2e8d7a4845cf9e800bf90b2b96f48f501741",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 44, 31, 157, 23, 148, 7, 43, 65, 109, 239, 29, 229, 145, 55, 171, 110, 221, 121, 238, 145, 150, 106, 101, 133, 138, 167, 50, 209, 228, 18, 112, 74, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}