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: 12aa84c7716360f3144a35157d5c3b520d4a95aa9c1251f77d092c97cb3b55e2
Tx prefix hash: bb40eeea22df15a973e2c0f2582cfcb8f3666ed130d086cfb4434e02796e86c4
Tx public key: d1f30dc0ae16c5911e448c8659556a1289b596dfa69500abfcd399b7a91f50b8
| Timestamp: 1780981480 | Timestamp [UTC]: 2026-06-09 05:04:40 | Age [y:d:h:m:s]: 00:000:09:44:15 |
| Block: 8039 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 603 | RingCT/type: yes/0 |
| Extra: 01d1f30dc0ae16c5911e448c8659556a1289b596dfa69500abfcd399b7a91f50b8020900000001e49593ff00 | ||
1 output(s) for total of 34.649064487047 HMNY
| stealth address | amount | amount idx | tag |
| 00: f711a87583d0e08e6d83eee2b3364fc610b7d33f8a9cf9493baa96695553c620 | 34.649064487047 | 9965 of 0 | <45> |
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": 8099,
"vin": [ {
"gen": {
"height": 8039
}
}
],
"vout": [ {
"amount": 34649064487047,
"target": {
"tagged_key": {
"key": "f711a87583d0e08e6d83eee2b3364fc610b7d33f8a9cf9493baa96695553c620",
"view_tag": "45"
}
}
}
],
"extra": [ 1, 209, 243, 13, 192, 174, 22, 197, 145, 30, 68, 140, 134, 89, 85, 106, 18, 137, 181, 150, 223, 166, 149, 0, 171, 252, 211, 153, 183, 169, 31, 80, 184, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}