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: f76555ba2bf1e454bfb394ef9f515ae8b0a4fbc0fe5cee284d61e53f5c8c482b
Tx prefix hash: 728e29cb29d815bb062ef3f3b9af5eecacfb1e05bf441e67b522cb2e7f6944bb
Tx public key: 1538956fe781df9e111d6cd039888358b7e88445ac8ef8e8f4e62d9180094465
| Timestamp: 1779949328 | Timestamp [UTC]: 2026-05-28 06:22:08 | Age [y:d:h:m:s]: 00:011:19:13:49 |
| Block: 3600 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4286 | RingCT/type: yes/0 |
| Extra: 011538956fe781df9e111d6cd039888358b7e88445ac8ef8e8f4e62d918009446502090000000126697be300 | ||
1 output(s) for total of 34.943674144307 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56b60e065f71c60b74ad7a84f591c97e5bf2b1d44c7312bd851ab5a4bf319d17 | 34.943674144307 | 4347 of 0 | <85> |
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": 3660,
"vin": [ {
"gen": {
"height": 3600
}
}
],
"vout": [ {
"amount": 34943674144307,
"target": {
"tagged_key": {
"key": "56b60e065f71c60b74ad7a84f591c97e5bf2b1d44c7312bd851ab5a4bf319d17",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 21, 56, 149, 111, 231, 129, 223, 158, 17, 29, 108, 208, 57, 136, 131, 88, 183, 232, 132, 69, 172, 142, 248, 232, 244, 230, 45, 145, 128, 9, 68, 101, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}