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: af02dbdf7ebc72545f1be2e2ab16ed3b88cf79fa1723a761ab2a2595d62d2fe0
Tx prefix hash: 3e65462f2b339d9f9b0c3482ce0c52cd90292a2febaddcab5fe81d0ca0dc6679
Tx public key: 88a37c59e3b758def83616f4e91c6689d9971c89b3d5431e1af5c0b84664baf9
| Timestamp: 1780690561 | Timestamp [UTC]: 2026-06-05 20:16:01 | Age [y:d:h:m:s]: 00:003:20:53:02 |
| Block: 5668 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3066 | RingCT/type: yes/0 |
| Extra: 0188a37c59e3b758def83616f4e91c6689d9971c89b3d5431e1af5c0b84664baf9020900000002e49593ff00 | ||
1 output(s) for total of 34.806113765332 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1fb55b0ef3d5c2185d5488f7a323917062c008e493dd089fcfc23af86304bb88 | 34.806113765332 | 7117 of 0 | <94> |
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": 5728,
"vin": [ {
"gen": {
"height": 5668
}
}
],
"vout": [ {
"amount": 34806113765332,
"target": {
"tagged_key": {
"key": "1fb55b0ef3d5c2185d5488f7a323917062c008e493dd089fcfc23af86304bb88",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 136, 163, 124, 89, 227, 183, 88, 222, 248, 54, 22, 244, 233, 28, 102, 137, 217, 151, 28, 137, 179, 213, 67, 30, 26, 245, 192, 184, 70, 100, 186, 249, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}