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: f561dd1fb8b72fdca41fb554d723c22e9a99889f9c9f43b5a8ed6b826b0aa1ee
Tx prefix hash: 429a981284ee523e54a2a401e1094aa5ba7c3fc88a152becb8589d3d0a9b00d2
Tx public key: dc036b06716d67b5995554ba1ea3420763c5fb2c66445661508444230b67164a
| Timestamp: 1779994765 | Timestamp [UTC]: 2026-05-28 18:59:25 | Age [y:d:h:m:s]: 00:011:05:47:22 |
| Block: 4017 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3869 | RingCT/type: yes/0 |
| Extra: 01dc036b06716d67b5995554ba1ea3420763c5fb2c66445661508444230b67164a02090000000226697be300 | ||
1 output(s) for total of 34.918510613939 HMNY
| stealth address | amount | amount idx | tag |
| 00: bba078ea531400e20dc6db23e17623f8e1ca3be7d1a7141d959c1ea2b1e5e57d | 34.918510613939 | 4968 of 0 | <40> |
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": 4077,
"vin": [ {
"gen": {
"height": 4017
}
}
],
"vout": [ {
"amount": 34918510613939,
"target": {
"tagged_key": {
"key": "bba078ea531400e20dc6db23e17623f8e1ca3be7d1a7141d959c1ea2b1e5e57d",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 220, 3, 107, 6, 113, 109, 103, 181, 153, 85, 84, 186, 30, 163, 66, 7, 99, 197, 251, 44, 102, 68, 86, 97, 80, 132, 68, 35, 11, 103, 22, 74, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}