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: 2582eacc7a038a41c8c31111824b9e95f6d01a4e3023978ec3aabb9de6f7d8c6
Tx prefix hash: 98dd4da3f9a5ad8126ae32c5ee90d1500b8c97e6fb5f1a89a03e4ea15347ba2a
Tx public key: d09e89cc1a54c6ddee8a2f71b24befb968b90f9571c55615b349e8d4f394499d
| Timestamp: 1779767769 | Timestamp [UTC]: 2026-05-26 03:56:09 | Age [y:d:h:m:s]: 00:013:21:39:48 |
| Block: 1983 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5903 | RingCT/type: yes/0 |
| Extra: 01d09e89cc1a54c6ddee8a2f71b24befb968b90f9571c55615b349e8d4f394499d02090000000126697be300 | ||
1 output(s) for total of 35.051613290352 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a72463fec0b51e8540097fe8d6544cb5226d8db233da53e08a33d3026f33c12 | 35.051613290352 | 2257 of 0 | <26> |
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": 2043,
"vin": [ {
"gen": {
"height": 1983
}
}
],
"vout": [ {
"amount": 35051613290352,
"target": {
"tagged_key": {
"key": "5a72463fec0b51e8540097fe8d6544cb5226d8db233da53e08a33d3026f33c12",
"view_tag": "26"
}
}
}
],
"extra": [ 1, 208, 158, 137, 204, 26, 84, 198, 221, 238, 138, 47, 113, 178, 75, 239, 185, 104, 185, 15, 149, 113, 197, 86, 21, 179, 73, 232, 212, 243, 148, 73, 157, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}