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: 72c5aa8e18b2277c131efd5c472a98d593ae6f7a808c063c58cd3a43cf6ac78f
Tx prefix hash: 96c1ac0dbc81ffda6aefe3f4e90ed4c7763faf436745223df81c5f44da15f700
Tx public key: 894bf6b5e9ae8cce85126a90dd20c2c775ce9b8c85e727ae8b027d34b6c92038
| Timestamp: 1780995703 | Timestamp [UTC]: 2026-06-09 09:01:43 | Age [y:d:h:m:s]: 00:000:08:07:20 |
| Block: 8327 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 408 | RingCT/type: yes/0 |
| Extra: 01894bf6b5e9ae8cce85126a90dd20c2c775ce9b8c85e727ae8b027d34b6c92038020900000002e49593ff00 | ||
1 output(s) for total of 34.630036396016 HMNY
| stealth address | amount | amount idx | tag |
| 00: c6a4688133ce3ececafc0fdef660ac5cc9a6ffe24d04f6f24314498ef77c3f4c | 34.630036396016 | 10301 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": 8387,
"vin": [ {
"gen": {
"height": 8327
}
}
],
"vout": [ {
"amount": 34630036396016,
"target": {
"tagged_key": {
"key": "c6a4688133ce3ececafc0fdef660ac5cc9a6ffe24d04f6f24314498ef77c3f4c",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 137, 75, 246, 181, 233, 174, 140, 206, 133, 18, 106, 144, 221, 32, 194, 199, 117, 206, 155, 140, 133, 231, 39, 174, 139, 2, 125, 52, 182, 201, 32, 56, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}