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: e5a3f8489d5b77d4cec2b71d5e610a5215aaf56a71f367fabf2a78b2ba1b0b39
Tx prefix hash: 010745954245e4f52918d51446a000da2b38db86997185b272dafa17b8012c2b
Tx public key: 5414376a09fd20796912ff2d41501d2f6280fc2814cfa0f18df0e65c91ebcb66
| Timestamp: 1779942100 | Timestamp [UTC]: 2026-05-28 04:21:40 | Age [y:d:h:m:s]: 00:011:23:29:18 |
| Block: 3514 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4467 | RingCT/type: yes/0 |
| Extra: 015414376a09fd20796912ff2d41501d2f6280fc2814cfa0f18df0e65c91ebcb6602090000000226697be300 | ||
1 output(s) for total of 34.949406500049 HMNY
| stealth address | amount | amount idx | tag |
| 00: 09623441d9360ab8edf1e56d16ade827ec4ac5b5d99f41190faedd74e43b24e0 | 34.949406500049 | 4238 of 0 | <a7> |
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": 3574,
"vin": [ {
"gen": {
"height": 3514
}
}
],
"vout": [ {
"amount": 34949406500049,
"target": {
"tagged_key": {
"key": "09623441d9360ab8edf1e56d16ade827ec4ac5b5d99f41190faedd74e43b24e0",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 84, 20, 55, 106, 9, 253, 32, 121, 105, 18, 255, 45, 65, 80, 29, 47, 98, 128, 252, 40, 20, 207, 160, 241, 141, 240, 230, 92, 145, 235, 203, 102, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}