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: 756e6f1f706326b36b988bf21d3635247fb98b17c7f768a2eb307ead5283b0f8
Tx prefix hash: 9c49dc26b307bf23cb558b267c7d91ddb5733812443e751264656f5a4f623a04
Tx public key: 692f79c8f86b2dc8b80dedb02fae3687173c0e66489f5b88306ad115fa5dfa2a
| Timestamp: 1779647078 | Timestamp [UTC]: 2026-05-24 18:24:38 | Age [y:d:h:m:s]: 00:015:09:14:12 |
| Block: 1456 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6493 | RingCT/type: yes/0 |
| Extra: 01692f79c8f86b2dc8b80dedb02fae3687173c0e66489f5b88306ad115fa5dfa2a020900000002ba6d17be00 | ||
1 output(s) for total of 35.086863963313 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1a16f3929582cc69e171499a0f44a12b32ce353880db0da8cb2e953a3c1ac587 | 35.086863963313 | 1610 of 0 | <7d> |
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": 1516,
"vin": [ {
"gen": {
"height": 1456
}
}
],
"vout": [ {
"amount": 35086863963313,
"target": {
"tagged_key": {
"key": "1a16f3929582cc69e171499a0f44a12b32ce353880db0da8cb2e953a3c1ac587",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 105, 47, 121, 200, 248, 107, 45, 200, 184, 13, 237, 176, 47, 174, 54, 135, 23, 60, 14, 102, 72, 159, 91, 136, 48, 106, 209, 21, 250, 93, 250, 42, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}