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: d000a622fe6f5c41663e15f3b5c5eb7e18af8ae1beb9ed40709d21788f38853a
Tx prefix hash: d0a234aadc64d7c8233b2f8926df87c8c280325b131fe7e450512adbac28ea73
Tx public key: 180e495d087a6f964616c7f95ff67f70c3c1acc1ea455fd269eba80e4a4d01f8
| Timestamp: 1779856382 | Timestamp [UTC]: 2026-05-27 04:33:02 | Age [y:d:h:m:s]: 00:012:16:39:05 |
| Block: 2624 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5262 | RingCT/type: yes/0 |
| Extra: 01180e495d087a6f964616c7f95ff67f70c3c1acc1ea455fd269eba80e4a4d01f802090000000126697be300 | ||
1 output(s) for total of 35.008784966495 HMNY
| stealth address | amount | amount idx | tag |
| 00: 256489cfac65f93e1184d31c5eab3099254cf9feba0f9080904e49dbff326af0 | 35.008784966495 | 3090 of 0 | <55> |
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": 2684,
"vin": [ {
"gen": {
"height": 2624
}
}
],
"vout": [ {
"amount": 35008784966495,
"target": {
"tagged_key": {
"key": "256489cfac65f93e1184d31c5eab3099254cf9feba0f9080904e49dbff326af0",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 24, 14, 73, 93, 8, 122, 111, 150, 70, 22, 199, 249, 95, 246, 127, 112, 195, 193, 172, 193, 234, 69, 95, 210, 105, 235, 168, 14, 74, 77, 1, 248, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}