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: dd44758a001b05b4e5f11d5121089aba267aed2700f8e79304338da60b19c47f
Tx prefix hash: 59b4e87a5f6e4723695feec4ccc0479a8866ac806aa64799a41285ecda0072c8
Tx public key: 0ba1a771e5cf3fb29b6b5767562a65da6035a121d1a161e310c27fcd5f5e5fec
| Timestamp: 1779638257 | Timestamp [UTC]: 2026-05-24 15:57:37 | Age [y:d:h:m:s]: 00:015:09:38:20 |
| Block: 1188 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6698 | RingCT/type: yes/0 |
| Extra: 010ba1a771e5cf3fb29b6b5767562a65da6035a121d1a161e310c27fcd5f5e5fec020900000001ba6d17be00 | ||
1 output(s) for total of 35.104803897583 HMNY
| stealth address | amount | amount idx | tag |
| 00: e5c0b0399b2d7a02bca6c57a164bb5207f8d4550c5d6b05d3b6c40f0fc15c59e | 35.104803897583 | 1332 of 0 | <94> |
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": 1248,
"vin": [ {
"gen": {
"height": 1188
}
}
],
"vout": [ {
"amount": 35104803897583,
"target": {
"tagged_key": {
"key": "e5c0b0399b2d7a02bca6c57a164bb5207f8d4550c5d6b05d3b6c40f0fc15c59e",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 11, 161, 167, 113, 229, 207, 63, 178, 155, 107, 87, 103, 86, 42, 101, 218, 96, 53, 161, 33, 209, 161, 97, 227, 16, 194, 127, 205, 95, 94, 95, 236, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}